dicklesworthstone/frankentorch

0

/ 100

Documentation65
Engineering84
Health100
Rust12Other1d ago
Grade a repo

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

Memory-safe clean-room Rust reimplementation of PyTorch with deterministic autograd contracts, strict/hardened compatibility modes, differential conformance harnesses, and RaptorQ-backed durability artifacts.

Documentation

65

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt55

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

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 (crates/ft-api/tests).

CI/CD14pt100

CI is configured (.github/workflows/phase2c_reliability_gates.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)
  • 3
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files33 root entries
  • .beads
    Good: .gitignore present.
  • .github
    Good: CI is configured (.github/workflows/phase2c_reliability_gates.yml).
  • artifacts
  • benchmarks
  • crates
    Good: Test files detected (crates/ft-api/tests).
  • docs
  • fuzz
  • hooks
  • scripts
  • tests
  • .gitignore
  • .skill-loop-progress.md
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • COMPREHENSIVE_SPEC_FOR_FRANKENSQLITE_V1_REFERENCE.md
  • COMPREHENSIVE_SPEC_FOR_FRANKENTORCH_V1.md
  • EXECUTION_TODO_GRANULAR.md
  • EXHAUSTIVE_LEGACY_ANALYSIS.md
  • EXISTING_PYTORCH_STRUCTURE.md
  • FEATURE_PARITY.md
  • FRANKENSQLITE_ADAPTATION_CROSSWALK.md
  • frankentorch_illustration.webp
  • gh_og_share_image.png
  • LICENSE
    Good: Licensed under Other.
  • PARITY-COVERAGE.md
  • PHASE2C_EXTRACTION_PACKET.md
  • PLAN_TO_PORT_PYTORCH_TO_RUST.md
  • PROFILING-RESULTS.md
  • PROPOSED_ARCHITECTURE.md
  • 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
  • rust-toolchain.toml