0
/ 100
Well engineered. The main gaps are issue and PR templates and a contributing guide.
A pure-rust secp256k1 library optimised for fun
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.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
If this crate also ships a binary, commit Cargo.lock. For pure library crates, omitting it is recommended per the Cargo guide.
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 0BSD.
Engineering
82
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.
No Cargo.lock committed (correct for Rust library crates; the ecosystem convention is to omit it for libraries).
Test files detected (ecdsa_fun/tests).
CI is configured (.github/workflows/test.yml).
Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
Project health
89
Last pushed 3-6 months ago (−40 pts). A push within 90 days earns 80 pts; within 30 days earns 100 pts.
→ A recent commit keeps the project looking alive to visitors and contributors.
Dependency manifest found (Cargo.toml).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 34Forks
- 0Releases
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 112Watchers
Responsiveness
- 11d 6hMedian issue response
- 2hMedian PR merge time
- 7Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).
- arithmetic_macros
- ecdsa_funGood: Test files detected (ecdsa_fun/tests).
- schnorr_fun
- secp256kfun
- sigma_fun
- vrf_fun
- .gitignoreGood: .gitignore present.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CLAUDE.md
- clippy.toml
- config.toml
- LICENSEGood: Licensed under 0BSD.
- publish.sh
- 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.
- rustfmt.tomlGood: Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/llfourn/secp256kfun)