inkandswitch/backstitch

0

/ 100

Documentation85
Engineering42
Health100
Rust127MIT1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Backstitch: Real-Time Version Control for Godot

Documentation

85

README12pt75

README is present.

Contributing guide5pt84

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

42

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

CI/CD14pt83

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

Linting and formatting5pt100

Rust linting configured (cargo clippy in CI, cargo fmt in CI).

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)
  • 7
    Forks
  • 38
    Releaseslatest 10mo ago

Community

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

Responsiveness

  • 19d 6h
    Median issue response
  • 3h
    Median PR merge time
  • 68
    Open issues
Repository files19 root entries
  • .cargo
  • .github
    Good: CI is configured (.github/workflows/linux_builds.yml).
  • .scripts
  • .vscode
  • assets
  • public
  • rust
  • scripts
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • backstitch_logo_banner.svg
  • backstitch-screenshot.png
  • build.env
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    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.
  • justfile
  • 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.
    Issue: 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.
    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.