79
/ 100
Strong early engineering with some momentum.
co/core is a place where people share the compute they already own to run AI for each other, instead of renting from a handful of giant providers
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 2License6pt
Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
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
62
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
85
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.
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Test files detected (infra/advisor/src/attest.test.ts).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (devDependency in package.json).
Project health
92
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)
- 8Forks
- 17Releaseslatest 1mo ago
Community
- 37% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 33Watchers
Responsiveness
- 2hMedian issue response
- <1hMedian PR merge time
- 15Open issues
Repository files26 root entries
- .agents
- .cursor
- .githubGood: CI is configured (.github/workflows/ci.yml).
- docs
- infraGood: Test files detected (infra/advisor/src/attest.test.ts).Good: Environment pinned via infra/advisor/Dockerfile.
- lexicons
- packages
- provider
- provider-shell
- scripts
- sdk
- .gitignoreGood: .gitignore present.
- .mcp.json
- .npmrc
- .oxfmtrc.json
- .oxlintrc.json
- CLAUDE.md
- hk.pkl
- knip.jsonc
- Makefile
- mise.toml
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- 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.
- skills-lock.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/graze-social/cocore)