79/ 100 · C
Good community traction and solid fundamentals. Nearly in the top tier.
a multi-language bindings generator for rust
Rust4,669 starsMPL-2.0updated 4d ago
DocumentationREADME, setup, examples, license
EngineeringTests, CI, linting, lockfiles
Project healthDescription, activity, stars, deps
What to fix first
The highest-impact improvements for this repo.
- 1READMEDocumentationWarning
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2READMEDocumentationInfo
Show a quick-start snippet so contributors can see what using your project looks like.
- 3READMEDocumentationInfo
Add CI/build status badges from shields.io or your CI provider to signal project health.
Detailed breakdown
Documentation
80- README55
- README is present.
- README is well structured with multiple sections.
- No screenshots or images in the README (−20 pts).Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- README has no code examples (−15 pts).Show a quick-start snippet so contributors can see what using your project looks like.
- README links to a live demo or deployed app.
- No status badges in the README (−10 pts).Add CI/build status badges from shields.io or your CI provider to signal project health.
- Install and run instructions90
- README documents how to install the project.
- README documents how to run the project.
- If your project uses environment variables, add a .env.example listing them (+10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
- License100
- Licensed under MPL-2.0.
- Contributing guide95
- Contributing guide is detailed and thorough.
- Contributing guide includes setup/install instructions.
- Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).
- Contributing guide explains how to run tests.
- Contributing guide describes the PR/review workflow.
- Contributing guide includes code examples.
- Code of conduct present.
Engineering
74- Tests90
- Test files detected (bindgen-tests/kotlin/enum-payload-clash/tests).
- Rust workspace with test files detected. Run with `cargo test --workspace`.
- CI/CD100
Not applicable?
- CI is configured (.circleci/config.yml).
- Linting and formatting40
- Rust projects have clippy available. Run `cargo clippy` for linting.
- CI does not appear to run `cargo clippy` (−40 pts vs enforcing it in CI).Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps.
- No rustfmt.toml found.Add a rustfmt.toml to enforce a consistent code style across contributors.
- Reproducibility70
- Lockfile present (Cargo.lock). Installs are reproducible.
- No Dockerfile or runtime version pin found. Adding one earns +10 pts.Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- No Dependabot config (adding it earns up to +20 pts).Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- Issue and PR templates0
- No issue or PR templates found (−90 pts).Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.
Project health
92- Dependency manifest100
- Dependency manifest found (Cargo.toml).
- Cargo.toml is a workspace manifest for a multi-crate Rust project.
- Repository metadata70
- Repository has a description.
- Primary language detected: Rust.
- Activity100
- Actively maintained (pushed within the last month).
- 4,669 stars.
- Housekeeping100
- .gitignore present.
Repository files31 root entries
- .cargo
- .circleciGood: CI is configured (.circleci/config.yml).
- .github
- bindgen-testsGood: Test files detected (bindgen-tests/kotlin/enum-payload-clash/tests).
- docker
- docs
- examples
- fixtures
- tools
- uniffi
- uniffi_bindgen
- uniffi_build
- uniffi_core
- uniffi_internal_macros
- uniffi_macros
- uniffi_meta
- uniffi_pipeline
- uniffi_testing
- uniffi_udl
- weedle2
- .dockerignore
- .gitignoreGood: .gitignore present.
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Info: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- LICENSEGood: Licensed under MPL-2.0.
- mkdocs.yml
- README.mdGood: README is present.Good: README is well structured with multiple sections.Warning: 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.Info: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Info: 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.
- release.toml
- rust-toolchain.toml