0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Rust interposition layer for glibc: transparent safety membrane that incrementally replaces C library functions with memory-safe Rust implementations
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 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
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
68
No Rust linting or formatting enforced.
→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.
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).
CI is configured (.github/workflows/ci.yml).
Test files detected (crates/frankenlibc-abi/tests).
Project health
100
Dependency manifest found (Cargo.toml).
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)
- 3Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 48Watchers
Responsiveness
- 19hMedian issue response
- -Median PR merge time
- 0Open issues
Repository files34 root entries
- .beadsGood: .gitignore present.
- .cargo
- .claude
- .dcg
- .githubGood: CI is configured (.github/workflows/ci.yml).
- artifacts
- configs
- cratesGood: Test files detected (crates/frankenlibc-abi/tests).
- data
- docker
- docsGood: 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.
- packaging
- scripts
- testsGood: Environment pinned via tests/cve_arena/Dockerfile.
- tools
- .dockerignore
- .gitignore
- .skill-loop-progress.md
- AGENTS.md
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- COMPATIBILITY.md
- DEPLOYMENT.md
- EXISTING_GLIBC_STRUCTURE.md
- FEATURE_PARITY.md
- LICENSEGood: Licensed under Other.
- PARITY-COVERAGE.md
- PLAN_TO_PORT_GLIBC_TO_RUST.md
- PROPOSED_ARCHITECTURE.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.
- REALITY_CHECK_BRIDGE_PLAN.md
- rust-toolchain.toml
- SECURITY.mdGood: Security policy present.
- support_matrix.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/dicklesworthstone/frankenlibc)