0
/ 100
Solid engineering. The main gap is visibility.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 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
78
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
78
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.
Test files detected (server/crates/djinn-agent-worker/tests).
Lockfile present (.npm-cache/_npx/1d6e82a4126006c4/package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/cla.yml).
Linter or formatter configured (ui/eslint.config.js).
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (.npm-cache/_npx/1d6e82a4126006c4/package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 2Forks
- 58Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 6Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 5Open issues
Repository files22 root entries
- .djinnGood: .gitignore present.
- .githubGood: CI is configured (.github/workflows/cla.yml).
- .npm
- .npm-cacheGood: Lockfile present (.npm-cache/_npx/1d6e82a4126006c4/package-lock.json). Installs are reproducible.Good: Dependency manifest found (.npm-cache/_npx/1d6e82a4126006c4/package.json).
- deploy
- docs
- scripts
- serverGood: Test files detected (server/crates/djinn-agent-worker/tests).
- uiGood: Linter or formatter configured (ui/eslint.config.js).
- website
- .dockerignore
- .gitignore
- CLA.md
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- LICENSEGood: Licensed under Other.
- Makefile
- 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.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.
- Tiltfile
- wave3-8cd0-direct-api.md
- wave3-8cd0-kill-bundle.md
- wave3-wu8h-direct-api.md
- wave3-wu8h-force-close-bundle.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/djinnos/djinn)