87
/ 100
A landmark open source project with strong engineering quality.
A modern runtime for JavaScript and TypeScript.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
81
README documents how to install the project.
CONTRIBUTING guide found.
README is present.
Licensed under MIT.
Engineering
93
Lockfile present (Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/cargo_publish.generated.yml).
Test files detected (cli/tools/test).
Rust linting configured (.editorconfig).
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 515 / 2101Commits (30d / 90d)
- 6,104Forks
- 384Releaseslatest 7y ago
Community
- 100% - GoodCommunity health
- 6 bus factorauthors own >50% of commits
- 107,406Watchers
Responsiveness
- <1hMedian issue response
- 4hMedian PR merge time
- 1,329Open issues
Repository files29 root entries
- .cargo
- .claude
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .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: Code of conduct present.Good: CI is configured (.github/workflows/cargo_publish.generated.yml).Good: Issue or PR templates present.Good: Security policy present.
- cliGood: Test files detected (cli/tools/test).
- doc
- ext
- libs
- runtime
- testsIssue: Build artifacts or local files may be committed (tests/registry/npm/@denotest/bundled-add/1.0.0/node_modules/@denotest) (−40 pts).Fix: Remove them and add to .gitignore.
- tools
- .dlint.json
- .dprint.json
- .editorconfigGood: Rust linting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .rustfmt.toml
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- flake.lock
- flake.nix
- import_map.json
- LICENSE.mdGood: Licensed under MIT.
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- Releases.md
- rust-toolchain.toml
- x
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/denoland/deno)