88
/ 100
Polished and well engineered. Punching above its star count.
Open-source control plane for your AI agents. Connect tools, hire agents, track every token and dollar
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
74
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
98
Lockfile present (bun.lock). Installs are reproducible.
Test files detected (apps/mesh/ct/tests).
CI is configured (.github/workflows/test.yml).
Linter or formatter configured (biome.json).
Issue or PR templates present.
Project health
86
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 51Forks
- 1000Releaseslatest 4mo ago
Community
- 62% - FairCommunity health
- 4 bus factorauthors own >50% of commits
- 380Watchers
Responsiveness
- 28d 15hMedian issue response
- <1hMedian PR merge time
- 93Open issues
Repository files33 root entries
- .claude
- .conductor
- .cursor
- .githooks
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Issue or PR templates present.
- .planning
- .superpowers
- .vscode
- appsGood: Test files detected (apps/mesh/ct/tests).Good: Environment pinned via apps/mesh/Dockerfile.
- decostudio-alias
- deploy
- packages
- plugins
- scripts
- tests
- .cursorindexingignore
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- .npmrc
- .oxlintrc.json
- AGENTS.md
- biome.jsonGood: Linter or formatter configured (biome.json).
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- CLAUDE.md
- knip.jsonc
- lefthook.yml
- LICENSE.mdGood: Licensed under Other.
- MAINTAINERS.txt
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.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.
- TESTING.md
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/decocms/studio)