rust-lang/libc

0

/ 100

Documentation83
Engineering84
Health98
Rust2,562Apache-2.01d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

Raw bindings to platform APIs for Rust

Documentation

83

README12pt70

README is present.

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

84

CI/CD14pt72

CI is configured (.github/workflows/ci.yaml).

Tests18pt80

Test files detected (ctest-test/tests).

Reproducibility6pt97

Lockfile present (Cargo.lock). Installs are reproducible.

Linting and formatting5pt100

Rust linting configured (.editorconfig, cargo clippy in CI).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

98

Dependency manifest6pt95

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 1,265
    Forks
  • 121
    Releaseslatest 6y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,562
    Watchers

Responsiveness

  • 3h
    Median issue response
  • 7h
    Median PR merge time
  • 217
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yaml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • ci
    Good: Environment pinned via ci/docker/aarch64-linux-android/Dockerfile.
  • ctest
  • ctest-test
    Good: Test files detected (ctest-test/tests).
  • libc-test
  • src
  • tests
  • .editorconfig
    Good: Rust linting configured (.editorconfig, cargo clippy in CI).
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .release-plz.toml
  • .rustfmt.toml
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: 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.md
    Good: 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