0
/ 100
Well engineered for its size. A portfolio piece worth showing off.
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.
- 2Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 3Contributing guide5pt
Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- 4Repository metadata5pt
Add a one-line description in the repo Settings → About. It appears in search results and social previews.
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
96
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
A license file is present.
Engineering
90
Test files detected (qcut/.agents/skills/qcut-toolkit/qcut-shot/scripts/lib.test.ts).
Lockfile present (qcut/.agents/skills/qcut-toolkit/baoyu/baoyu-format-markdown/scripts/bun.lock). Installs are reproducible.
CI is configured (.github/workflows/build-aicp-binaries.yml).
Linter or formatter configured (qcut/biome.jsonc).
Issue or PR templates present.
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 (qcut/.agents/skills/qcut-toolkit/baoyu/baoyu-format-markdown/scripts/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)
- 4Forks
- 184Releaseslatest 5mo ago
Community
- -Community health
- -authors own >50% of commits
- 28Watchers
Responsiveness
- <1hMedian issue response
- 1hMedian PR merge time
- 2Open issues
Repository files6 root entries
- .githubGood: CI is configured (.github/workflows/build-aicp-binaries.yml).
- qcutGood: A license file is present.Good: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: Test files detected (qcut/.agents/skills/qcut-toolkit/qcut-shot/scripts/lib.test.ts).Good: Linter or formatter configured (qcut/biome.jsonc).Good: Lockfile present (qcut/.agents/skills/qcut-toolkit/baoyu/baoyu-format-markdown/scripts/bun.lock). Installs are reproducible.Good: Environment pinned via qcut/apps/web/Dockerfile.Good: Issue or PR templates present.Good: Security policy present.Good: Dependency manifest found (qcut/.agents/skills/qcut-toolkit/baoyu/baoyu-format-markdown/scripts/package.json).
- .gitignoreGood: .gitignore present.
- .gitmodules
- codecov.yml
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/quriosity-agent/qcut)