A well-known project done right. Strong docs and solid engineering throughout.

Ethereum L1 Protocol Stack and EVM in TypeScript

Documentation

90

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

98

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (config/vitest.config.mts).

CI/CD14pt100

CI is configured (.github/workflows/build.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 848
    Forks
  • 442
    Releaseslatest 5y ago

Community

  • Community health
  • authors own >50% of commits
  • 2,753
    Watchers

Responsiveness

  • 7h
    Median issue response
  • 11h
    Median PR merge time
  • 135
    Open issues
Repository files29 root entries
  • .githooks
  • .github
    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: CI is configured (.github/workflows/build.yml).
    Good: Issue or PR templates present.
  • .vscode
  • config
    Good: Test files detected (config/vitest.config.mts).
  • docker
  • packages
    Good: A license file is present.
  • scripts
  • .cursorignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .npmrc
  • .nvmrc
  • ARCHITECTURE.md
  • biome.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • DEVELOPER.md
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • eslint.config.mjs
  • FUNDING.json
  • lint-staged.config.js
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: 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