0
/ 100
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.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 2README12pt
Link to a deployed version, docs site, or demo video. Users want to see it running.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
65
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.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
84
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.
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (crates/ft-api/tests).
CI is configured (.github/workflows/phase2c_reliability_gates.yml).
Rust linting configured (cargo clippy in CI, cargo fmt in CI).
Project health
100
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 3Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 12Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files33 root entries
- .beadsGood: .gitignore present.
- .githubGood: CI is configured (.github/workflows/phase2c_reliability_gates.yml).
- artifacts
- benchmarks
- cratesGood: Test files detected (crates/ft-api/tests).
- docs
- fuzz
- hooks
- scripts
- tests
- .gitignore
- .skill-loop-progress.md
- AGENTS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: 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
- LICENSEGood: Licensed under Other.
- PARITY-COVERAGE.md
- PHASE2C_EXTRACTION_PACKET.md
- PLAN_TO_PORT_PYTORCH_TO_RUST.md
- PROFILING-RESULTS.md
- PROPOSED_ARCHITECTURE.md
- README.mdGood: 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
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/dicklesworthstone/frankentorch)