web3infra-foundation/libra

0

/ 100

Documentation89
Engineering84
Health98
Rust72MIT1d ago
Grade a repo

Well engineered for its size. A portfolio piece worth showing off.

Libra is evolving into an AI agent–native version control tools

Documentation

89

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

84

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.

Reproducibility6pt70

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

Tests18pt100

Test files detected (tests).

CI/CD14pt100

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

Linting and formatting5pt100

Rust linting configured (rustfmt.toml, cargo clippy in CI).

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)
  • 159
    Forks
  • 54
    Releaseslatest 2mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 72
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 12h
    Median PR merge time
  • 10
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/base.yml).
  • docs
    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.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • sql
  • src
    Good: Security policy present.
  • template
  • tests
    Good: Test files detected (tests).
  • tools
  • web
  • worker
  • .env.test.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .libraignore
  • AGENTS.md
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • COMMAND_INTEGRATION_CONTRACT_OPERATION_LOG.md
  • COMPATIBILITY.md
  • install.sh
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    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.toml
    Good: Rust linting configured (rustfmt.toml, cargo clippy in CI).
  • TEST_CONTRACT_ FOR_OPERATION_LAYER.md
  • test.txt