dust-tt/dust
Grade a repo

0

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

Custom AI agent platform to speed up your work.

Documentation29
Engineering74
Health86
TypeScript1,399MITtoday

Documentation

29

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

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.

README12pt28

README is present.

License6pt100

Licensed under MIT.

Engineering

74

Tests18pt35

Test files detected (cli/dust-sandbox/tests).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

CI/CD14pt100

CI is configured (.github/workflows/build-and-lint-dust-hive.yml).

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (package.json).

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)
  • 291
    Forks
  • 28
    Releaseslatest 1mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,399
    Watchers

Responsiveness

  • 1d 7h
    Median issue response
  • 2h
    Median PR merge time
  • 221
    Open issues
Repository files58 root entries
  • .agents
  • .claude
  • .github
    Good: CI is configured (.github/workflows/build-and-lint-dust-hive.yml).
    Good: Issue or PR templates present.
  • .grit
  • .junie
  • .run
  • .vscode
  • cli
    Good: Test files detected (cli/dust-sandbox/tests).
    Good: Environment pinned via cli/dust-sandbox/e2e/Dockerfile.
  • connectors
  • core
  • design_docs
  • devbox.d
  • dockerfiles
  • egress-proxy
  • extension
  • firebase-functions
  • front
  • front-api
  • front-spa
  • marketing
  • preview-proxy
  • prodbox
  • sandbox
  • scripts
  • sdks
  • sparkle
  • tools
  • viz
  • x
  • .authors
  • .dockerignore
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .nvmrc
  • .vale.ini
  • AGENTS.md
  • biome.editor.json
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • CLAUDE.md
  • CODING_RULES.md
  • core.code-workspace
  • docker-compose.yml
  • doctor.config.json
  • dust.code-workspace
  • elasticsearch.Dockerfile
  • init_dev_container.sh
  • knip.ts
  • lefthook.yml
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • PRODUCT.md
  • README.md
    Good: README is present.
    Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.
  • socket.yml
  • SUPPORT.md
  • tika-config.xml