93
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Ethereum L1 Protocol Stack and EVM in TypeScript
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.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
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
90
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
A license file is present.
Engineering
98
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (config/vitest.config.mts).
CI is configured (.github/workflows/build.yml).
Linter or formatter configured (.editorconfig).
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)
- 849Forks
- 442Releaseslatest 5y ago
Community
- 50% - FairCommunity health
- 4 bus factorauthors own >50% of commits
- 2,755Watchers
Responsiveness
- 7hMedian issue response
- 11hMedian PR merge time
- 135Open issues
Repository files29 root entries
- .githooks
- .githubGood: 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: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- .vscode
- configGood: Test files detected (config/vitest.config.mts).
- docker
- packagesGood: A license file is present.
- scripts
- .cursorignore
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .gitmodules
- .npmrc
- .nvmrc
- ARCHITECTURE.md
- biome.json
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- codecov.yml
- DEVELOPER.md
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjs
- FUNDING.json
- lint-staged.config.js
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- 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.
- tsconfig.json
- tsconfig.lint.json
- tsconfig.prod.cjs.json
- tsconfig.prod.esm.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/ethereumjs/ethereumjs-monorepo)