Good community traction and solid fundamentals. Nearly in the top tier.

A bidirectional bindings generator for C++ and Rust.

Documentation

82

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt86

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

Add setup instructions, code style notes, and how to run tests.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

71

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.

Reproducibility6pt82

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

CI/CD14pt85

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

Tests18pt100

Test files detected (cargo/cc_bindings_from_rs/cargo-cpp_api_from_rust/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)
  • 66
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 1,040
    Watchers

Responsiveness

  • 3d 16h
    Median issue response
  • 21h
    Median PR merge time
  • 121
    Open issues
Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/rust.yml).
    Good: Dependabot configured for cargo.
  • assets
  • bazel
  • buildenv
  • cargo
    Good: Test files detected (cargo/cc_bindings_from_rs/cargo-cpp_api_from_rust/tests).
  • cc_bindings_from_rs
  • common
  • docs
  • doxygen
  • examples
  • features
  • lifetime_analysis
  • lifetime_annotations
  • migrator
  • nullability
  • patches
  • rs_bindings_from_cc
  • support
  • theme
  • .bazelrc
  • .bazelversion
  • .gitignore
    Good: .gitignore present.
  • book.toml
  • BUILD
  • BUILD.gn
  • Cargo.Bazel.lock
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CMakeLists.txt
  • CODE_OF_CONDUCT
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • crubit.gni
  • LICENSE
    Good: Licensed under Other.
  • MODULE.bazel
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rust-toolchain.toml
  • WORKSPACE.bzlmod