vm0-ai/vm0

0

/ 100

Documentation81
Engineering80
Health100
TypeScript1,130Other1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

Zero, your trustworthy AI teammate for real work.

Documentation

81

Install and run instructions9pt55

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

→ Add a section showing how to install dependencies.

README12pt85

README is present.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under Other.

Engineering

80

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.

Tests18pt80

Test files detected (.github/scripts/tests).

CI/CD14pt100

CI is configured (.github/workflows/cleanup.yml).

Linting and formatting5pt100

Linter or formatter configured (crates/rustfmt.toml).

Reproducibility6pt100

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (crates/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)
  • 69
    Forks
  • 1000
    Releaseslatest 15d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,130
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 104
    Open issues
Repository files33 root entries
  • .claude
  • .devcontainer
  • .github
    Good: Test files detected (.github/scripts/tests).
    Good: CI is configured (.github/workflows/cleanup.yml).
    Good: Dependabot covers 5 ecosystems (npm, npm, cargo, docker, github-actions). Dependencies stay current.
  • .vscode
  • ansible
  • assets
  • bin
  • crates
    Good: Linter or formatter configured (crates/rustfmt.toml).
    Good: Lockfile present (crates/Cargo.lock). Installs are reproducible.
    Good: Dependency manifest found (crates/Cargo.toml).
  • docker
    Good: Environment pinned via docker/toolchain/Dockerfile.
  • docs
  • e2e
  • scripts
  • turbo
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .gitmodules
  • .mailmap
  • .release-please-manifest.json
  • .semgrepignore
  • AGENTS.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • commitlint.config.mjs
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • lefthook.yml
  • LICENSE
    Good: Licensed under Other.
  • README.md
    Good: 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.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • release-please-config.json
  • REVIEW.md
  • SECURITY.md
    Good: Security policy present.
  • vm0.code-workspace