fedify-dev/fedify

0

/ 100

Documentation86
Engineering49
Health86
TypeScript989MIT1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

ActivityPub server framework in TypeScript

Documentation

86

README12pt75

README is present.

Contributing guide5pt87

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

49

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt35

Test files detected (packages/amqp/src/mq.test.ts).

CI/CD14pt57

CI is configured (.github/workflows/build.yaml).

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (examples/next-integration/eslint.config.mjs).

Project health

86

Dependency manifest6pt55

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 104
    Forks
  • 304
    Releaseslatest 2y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 989
    Watchers

Responsiveness

  • 8h
    Median issue response
  • 1h
    Median PR merge time
  • 54
    Open issues
Repository files43 root entries
  • .agents
  • .claude
  • .claude-plugin
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/build.yaml).
  • .vscode
  • .zed
  • claude-plugin
  • docs
  • examples
    Good: Linter or formatter configured (examples/next-integration/eslint.config.mjs).
    Good: Environment pinned via examples/monitoring/compose.yaml.
  • packages
    Good: Test files detected (packages/amqp/src/mq.test.ts).
  • schema
  • scripts
  • test
  • .cursorrules
  • .gitignore
    Good: .gitignore present.
  • .hongdown.toml
  • .issues-auto-labeler.json
  • .repomixignore
  • .windsurfrules
  • AGENT.md
  • AGENTS.md
  • AI_POLICY.md
  • CHANGES.md
  • CLAUDE.md
  • context7.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • cspell.json
  • deno.json
  • deno.lock
  • FEDERATION.md
  • GEMINI.md
  • LICENSE
    Good: Licensed under MIT.
  • logo.svg
  • mise.toml
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • repomix.config.json
  • SECURITY.md
    Good: Security policy present.
  • SPONSORS.md
  • WARP.md