94
/ 100
Well engineered for its size. A portfolio piece worth showing off.
Your AI agents never start from zero again. Local-first MCP runtime with persistent memory across sessions and tools.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4Contributing guide5pt
Add setup instructions, code style notes, and how to run tests.
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
93
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
92
CI is configured (.github/workflows/ci.yml).
Test files detected (docs/spec).
Linter or formatter configured (.prettierrc).
Lockfile present (package-lock.json). Installs are reproducible.
Issue or PR templates present.
Project health
100
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)
- 22Forks
- 17Releaseslatest 1mo ago
Community
- 100% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 27Watchers
Responsiveness
- 8hMedian issue response
- <1hMedian PR merge time
- 18Open issues
Repository files64 root entries
- .agents
- .clusterfuzzliteGood: Environment pinned via .clusterfuzzlite/Dockerfile.
- .codebuddy
- .codex
- .codex-plugin
- .cursor
- .gemini-plugin
- .githubIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.Good: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 3 ecosystems (npm, npm, github-actions). Dependencies stay current.Good: Issue or PR templates present.Good: Security policy present.
- .kiro
- .opencode
- .trae
- agents
- assets
- commands
- dashboard
- docker
- docsGood: Test files detected (docs/spec).
- examples
- fuzz
- hooks
- manifests
- mcp
- mcp-configs
- memory
- rules
- schemas
- scripts
- skills
- src
- tests
- translations
- .coderabbit.yaml
- .env.example
- .gitignoreGood: .gitignore present.
- .gitlab-ci.yml
- .markdownlint.json
- .mcp.json
- .mcp.json.example
- .npmignore
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- .sonarcloud.properties
- .tool-versions
- .yarnrc.yml
- agent.yaml
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- codecov.yml
- CONTRIBUTING.md
- crowdin.yml
- Dockerfile
- eslint.config.js
- GEMINI.md
- glama.json
- install.ps1
- install.sh
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pytest.ini
- 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.
- VERSION
- yarn.lock
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/fmarzochi/egc)