73
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Post-quantum cryptography certificates
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 B (83).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
74
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
54
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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/artifact_validation.yaml).
Lockfile present (src/requirements.txt). Installs are reproducible.
Test files detected (providers/openjdk/Test.java).
Project health
100
Dependency manifest found (cmp/bouncycastle/build.gradle.kts).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 12 / 18Commits (30d / 90d)
- 44Forks
- 0Releases
Community
- 37% - WeakCommunity health
- 3 bus factorauthors own >50% of commits
- 86Watchers
Responsiveness
- 9d 2hMedian issue response
- 12hMedian PR merge time
- 12Open issues
Repository files10 root entries
- .githubGood: CI is configured (.github/workflows/artifact_validation.yaml).
- cmpGood: Dependency manifest found (cmp/bouncycastle/build.gradle.kts).
- docs
- providersGood: Test files detected (providers/openjdk/Test.java).
- srcGood: Lockfile present (src/requirements.txt). Installs are reproducible.
- .gitattributes
- .gitignoreGood: .gitignore present.
- license.txtGood: Licensed under Other.
- Makefile
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/ietf-hackathon/pqc-certificates)