87
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Raw bindings to platform APIs for Rust
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add test/dev tooling under [dev-dependencies] so `cargo test` runs a complete suite.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 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
83
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
84
CI is configured (.github/workflows/ci.yaml).
Test files detected (ctest-test/tests).
Lockfile present (Cargo.lock). Installs are reproducible.
Rust linting configured (.editorconfig, cargo clippy in CI).
Issue or PR templates present.
Project health
98
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)
- 1,265Forks
- 121Releaseslatest 7y ago
Community
- 75% - GoodCommunity health
- -authors own >50% of commits
- 2,561Watchers
Responsiveness
- 3hMedian issue response
- 7hMedian PR merge time
- 217Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/ci.yaml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- ciGood: Environment pinned via ci/docker/aarch64-linux-android/Dockerfile.
- ctest
- ctest-testGood: Test files detected (ctest-test/tests).
- libc-test
- src
- tests
- .editorconfigGood: Rust linting configured (.editorconfig, cargo clippy in CI).
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .release-plz.toml
- .rustfmt.toml
- build.rs
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSE-APACHE
- LICENSE-MIT
- 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.
- triagebot.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/rust-lang/libc)