Solid foundation. Invest in docs and CI to grow from here.

Mesh based bevy text implementation.

Documentation

85

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

52

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.

Reproducibility6pt5

No Cargo.lock found (−70 pts). Rust binary/application crates should commit Cargo.lock.

Run `cargo build` and commit the resulting Cargo.lock file.

Tests18pt55

Cargo.toml has dev-dependencies (may include test tooling).

CI/CD14pt72

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

Linting and formatting5pt100

Rust linting configured (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)
  • 16
    Forks
  • 2
    Releaseslatest 11mo ago

Community

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

Responsiveness

  • 12h
    Median issue response
  • <1h
    Median PR merge time
  • 3
    Open issues
Repository files11 root entries
  • .github
    Good: CI is configured (.github/workflows/rust.yml).
  • assets
  • examples
  • showcase
  • src
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • LICENSE-APACHE
  • LICENSE-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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.