0
/ 100
Strong setup for a brand-new repo. Docs and CI already in good shape.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 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
90
README is present.
README documents how to install the project.
A license file is present.
Contributing guide is detailed and thorough.
Engineering
74
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (addons/resonant-browser-host/test).
CI is configured (.github/workflows/alpha-build.yml).
Project health
73
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 5Forks
- -Releases
Community
- 37% - WeakCommunity health
- -authors own >50% of commits
- 8Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 80Open issues
Repository files30 root entries
- .githubGood: CI is configured (.github/workflows/alpha-build.yml).
- addonsGood: Test files detected (addons/resonant-browser-host/test).
- browser-first
- build
- docs
- electron-host
- examples
- publicGood: A license file is present.
- scripts
- src
- src-tauri
- .gitignoreGood: .gitignore present.
- AGENTS.md
- AUDIT-ARCHITECTURE.md
- AUDIT-BROWSER-COMPLETENESS.md
- AUDIT-COMMUNITY.md
- AUDIT-SECURITY.md
- CHANGELOG-P0-FIXES.md
- CHANGELOG.md
- CODEBASE-EVALUATION-2026-06-07.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- index.html
- 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.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.Good: README documents how to run the project.
- rust-toolchain.toml
- SECURITY-RED-TEAM-REPORT.md
- SECURITY.mdGood: Security policy present.
- tsconfig.json
- vite.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/resonantos/2.0.0-alpha)