0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Efficient and versatile WebAssembly interpreter for embedded systems.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a section showing how to install dependencies.
- 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
75
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under Apache-2.0.
Engineering
98
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (crates/cli/tests).
CI is configured (.github/workflows/rust.yml).
Rust linting configured (cargo clippy in CI, cargo fmt in CI).
Issue or PR templates present.
Project health
100
Dependency manifest found (Cargo.toml).
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)
- 355Forks
- 88Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 2,140Watchers
Responsiveness
- 1d 5hMedian issue response
- 3hMedian PR merge time
- 30Open issues
Repository files21 root entries
- .cargo
- .config
- .githubGood: CI is configured (.github/workflows/rust.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- cratesGood: Test files detected (crates/cli/tests).
- docs
- fuzz
- resources
- .gitignoreGood: .gitignore present.
- .gitmodules
- .rustfmt.toml
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- codecov.yml
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSE-APACHE
- LICENSE-MIT
- NEWS.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/wasmi-labs/wasmi)