Good shape overall. A few tweaks would push it into the top tier.
Turn Your Work Into Content
Documentation
88
README12pt
70
README is present.
Contributing guide5pt
97
Contributing guide is detailed and thorough.
Install and run instructions9pt
100
README documents how to install the project.
License6pt
100
Licensed under AGPL-3.0.
Engineering
64
Tests18pt
35
Test files detected (packages/ai/src/integrations/mcp-tool-name.test.ts).
CI/CD14pt
57
CI is configured (.github/workflows/code-quality.yml).
Linting and formatting5pt
100
Linter or formatter configured (biome.jsonc).
Reproducibility6pt
100
Lockfile present (bun.lock). Installs are reproducible.
Issue and PR templates6pt
100
Issue or PR templates present.
Project health
89
Dependency manifest6pt
65
Dependency manifest found (package.json).
Repository metadata5pt
100
Repository has a description.
Activity5pt
100
Actively maintained (pushed within the last month).
Housekeeping3pt
100
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 38Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 130Watchers
Responsiveness
- <1hMedian issue response
- 1hMedian PR merge time
- 18Open issues
Repository files32 root entries
- .agents
- .claude
- .codex
- .cursor
- .expect
- .githubGood: CI is configured (.github/workflows/code-quality.yml).Good: Dependabot covers 2 ecosystems (bun, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .husky
- .opencode
- .stagewise
- .vscode
- appsGood: Environment pinned via apps/api/Dockerfile.
- packagesGood: Test files detected (packages/ai/src/integrations/mcp-tool-name.test.ts).
- scripts
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- .npmrc
- AGENTS.md
- biome.jsoncGood: Linter or formatter configured (biome.jsonc).
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- bunfig.toml
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- commitlint.config.ts
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under AGPL-3.0.
- package.jsonGood: Dependency manifest found (package.json).
- POST_GROUPS_PLAN.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.
- SECURITY.mdGood: Security policy present.
- skills-lock.json
- sonnet-generation-story.md
- turbo.json