85
/ 100
A top-tier open source project. Docs, tests, and CI are all in excellent shape.
⚓ A collection of high-performance JavaScript tools.
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.
- 2Install and run instructions9pt
Add a section showing how to install dependencies.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
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
72
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under MIT.
Engineering
98
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (apps/oxfmt/test).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
83
.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
- 804 / 2433Commits (30d / 90d)
- 1,115Forks
- 255Releaseslatest 3y ago
Community
- 100% - GoodCommunity health
- 3 bus factorauthors own >50% of commits
- 21,890Watchers
Responsiveness
- 5hMedian issue response
- <1hMedian PR merge time
- 644Open issues
Repository files43 root entries
- .agents
- .cargo
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: Code of conduct present.Good: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.Good: Security policy present.
- .vscode
- .zed
- appsGood: Test files detected (apps/oxfmt/test).Issue: Build artifacts or local files may be committed (apps/oxfmt/test/cli/init_with_schema/fixtures/node_modules/oxfmt) (−40 pts).Fix: Remove them and add to .gitignore.
- crates
- napi
- npm
- tasks
- .clippy.toml
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .git-blame-ignore-revs
- .gitattributes
- .gitignoreGood: .gitignore present.
- .ignore
- .node-version
- .rustfmt.toml
- .typos.toml
- AGENTS.md
- ARCHITECTURE.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CLAUDE.md
- cliff.toml
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
- Cross.toml
- deny.toml
- justfile
- LICENSEGood: Licensed under MIT.
- MAINTENANCE.md
- oxc_release.toml
- oxfmtrc.jsonc
- oxlintrc.json
- package.json
- pnpm-lock.yaml
- pnpm-workspace.yaml
- 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.Good: README includes status badges.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.
- rust-toolchain.toml
- THIRD-PARTY-LICENSE
- vite-task.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/oxc-project/oxc)