dstack-tee/dstack

0

/ 100

Documentation95
Engineering63
Health100
Rust501Apache-2.01d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Open framework for confidential AI

Documentation

95

Contributing guide5pt71

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

63

Linting and formatting5pt0

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.

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.

CI/CD14pt57

CI is configured (.github/workflows/docker-build-check.yml).

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (dstack-attest/tests).

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

Community

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

Responsiveness

  • 19h
    Median issue response
  • 5h
    Median PR merge time
  • 74
    Open issues
Repository files76 root entries
  • .agent
  • .claude
  • .github
    Good: CI is configured (.github/workflows/docker-build-check.yml).
  • basefiles
  • build
  • cc-eventlog
  • cert-client
  • certbot
  • ct_monitor
  • docs
  • dstack-attest
    Good: Test files detected (dstack-attest/tests).
  • dstack-mr
  • dstack-types
  • dstack-util
  • gateway
    Good: 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
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .mailmap
  • attestation.md
  • cargo-check-all.sh
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • cliff.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: 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
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • prek.toml
  • README.md
    Good: 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