0
/ 100
Rough and inactive. Tests, CI, and a fuller README would revive it.
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (79).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2README12pt
Add an Overview, Install, Usage, and Contributing section at minimum.
- 3README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 4README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
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
README is present.
CONTRIBUTING guide found.
README documents how to install the project.
A license file is present.
Engineering
61
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.
Test files detected (node_modules/@nodelib/fs.scandir/out/adapters/fs.spec.js).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (node_modules/acorn-node/.travis.yml).
Linter or formatter configured (node_modules/ajv/scripts/.eslintrc.yml).
Project health
32
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
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).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- -Releases
Community
- -Community health
- -authors own >50% of commits
- 1Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files8 root entries
- bundler
- dist
- node_modulesGood: A license file is present.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: Code of conduct present.Good: Test files detected (node_modules/@nodelib/fs.scandir/out/adapters/fs.spec.js).Good: CI is configured (node_modules/acorn-node/.travis.yml).Good: Linter or formatter configured (node_modules/ajv/scripts/.eslintrc.yml).Good: Environment pinned via node_modules/is-symbol/.nvmrc.Good: Security policy present.Issue: Build artifacts or local files may be committed (node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
- src
- static
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- readme.mdGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.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.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/aatvel/earth)