0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Produces secure keys and passwords. Supports SSH, PGP, BLS, OTP and many other formats
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
70
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
72
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.
CI is configured (.github/workflows/test-ts.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (test).
Linter or formatter configured (.prettierrc.json).
Project health
98
Dependency manifest found (package.json).
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)
- 15Forks
- 29Releaseslatest 2y ago
Community
- -Community health
- -authors own >50% of commits
- 75Watchers
Responsiveness
- <1hMedian issue response
- 3d 1hMedian PR merge time
- 3Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/test-ts.yml).
- .vscode
- benchmark
- bin
- src
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- .prettierrc.jsonGood: Linter or formatter configured (.prettierrc.json).
- jsr.json
- LICENSEGood: Licensed under MIT.
- 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.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.
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/paulmillr/micro-key-producer)