Well engineered for its size. A portfolio piece worth showing off.
Snapchain, made hyperdimensional
Documentation
82
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.
README is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
86
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 (src/tests).
CI is configured (.github/workflows/verify.yml).
Rust linting configured (cargo fmt in CI).
Project health
86
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)
- 23Forks
- 3Releaseslatest 1mo ago
Community
- —Community health
- —authors own >50% of commits
- 61Watchers
Responsiveness
- 3d 10hMedian issue response
- 4d 10hMedian PR merge time
- 13Open issues
Repository files24 root entries
- .githubGood: CI is configured (.github/workflows/verify.yml).
- config
- docs
- grafana
- proto
- scripts
- site
- srcGood: Test files detected (src/tests).
- tests
- .dockerignore
- .gitignoreGood: .gitignore present.
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- cliff.toml
- docker-compose.mainnet.yml
- docker-compose.nightly.yml
- docker-compose.testnet.yml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under GPL-3.0.
- Makefile
- README.mdGood: 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.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.
- validators.toml