0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Open framework for confidential AI
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
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
95
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
63
No Rust linting or formatting enforced.
→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.
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.
CI is configured (.github/workflows/docker-build-check.yml).
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (dstack-attest/tests).
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)
- 83Forks
- 38Releaseslatest 11mo ago
Community
- -Community health
- -authors own >50% of commits
- 501Watchers
Responsiveness
- 19hMedian issue response
- 5hMedian PR merge time
- 74Open issues
Repository files76 root entries
- .agent
- .claude
- .githubGood: CI is configured (.github/workflows/docker-build-check.yml).
- basefiles
- build
- cc-eventlog
- cert-client
- certbot
- ct_monitor
- docs
- dstack-attestGood: Test files detected (dstack-attest/tests).
- dstack-mr
- dstack-types
- dstack-util
- gatewayGood: Environment pinned via gateway/dstack-app/builder/Dockerfile.
- guest-agent
- guest-agent-simulator
- guest-api
- host-api
- http-client
- iohash
- key-provider-build
- key-provider-client
- kms
- LICENSES
- load_config
- lspci
- no_std_check
- nsm-attest
- nsm-qvl
- port-forward
- python
- ra-rpc
- ra-tls
- rocket-vsock-listener
- scripts
- sdk
- serde-duration
- sev-snp-attest
- sev-snp-qvl
- size-parser
- sodiumbox
- supervisor
- tdx-attest
- test-scripts
- tests
- tools
- tpm-attest
- tpm-qvl
- tpm-types
- tpm2
- verifier
- vmm
- .cursorrules
- .gitignoreGood: .gitignore present.
- .gitmodules
- .mailmap
- attestation.md
- cargo-check-all.sh
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CLAUDE.md
- cliff.toml
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.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.
- dstack_Technical_Charter_Final_10-17-2025.pdf
- dstack-logo.svg
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- prek.toml
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- REUSE.toml
- run-tests.sh
- run.sh
- 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/dstack-tee/dstack)