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

Documentation

93

Contributing guide5pt72

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

68

Linting and formatting5pt0

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.

Issue and PR templates6pt0

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.

Reproducibility6pt60

No Cargo.lock committed (correct for Rust library crates; the ecosystem convention is to omit it for libraries).

CI/CD14pt85

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

Tests18pt100

Test files detected (crates/frankenlibc-abi/tests).

Project health

100

Dependency manifest6pt100

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)
  • 3
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 48
    Watchers

Responsiveness

  • 19h
    Median issue response
  • Median PR merge time
  • 0
    Open issues
Repository files34 root entries
  • .beads
    Good: .gitignore present.
  • .cargo
  • .claude
  • .dcg
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • artifacts
  • configs
  • crates
    Good: Test files detected (crates/frankenlibc-abi/tests).
  • data
  • docker
  • docs
    Good: 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
  • tests
    Good: Environment pinned via tests/cve_arena/Dockerfile.
  • tools
  • .dockerignore
  • .gitignore
  • .skill-loop-progress.md
  • AGENTS.md
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • COMPATIBILITY.md
  • DEPLOYMENT.md
  • EXISTING_GLIBC_STRUCTURE.md
  • FEATURE_PARITY.md
  • LICENSE
    Good: Licensed under Other.
  • PARITY-COVERAGE.md
  • PLAN_TO_PORT_GLIBC_TO_RUST.md
  • PROPOSED_ARCHITECTURE.md
  • README.md
    Good: 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.md
    Good: Security policy present.
  • support_matrix.json