pomazanbohdan/vida-stack
Grade a repo

0

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

Top 33% of 5,156 graded repos

Vida Stack — an agentic engineering control plane for orchestrating autonomous product development.

Documentation83
Engineering69
Health100
Rust16MPL-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

16 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

83

Contributing guide5pt58

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.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MPL-2.0.

Engineering

69

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.

CI/CD14pt40

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

Reproducibility6pt70

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

Tests18pt100

Test files detected (crates/docflow-cli/tests).

Issue and PR templates6pt100

Issue or PR templates present.

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)
  • 0
    Forks
  • 26
    Releaseslatest 5mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 16
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 7h
    Median PR merge time
  • 3
    Open issues
Repository files38 root entries
  • .agents
  • .cargo
  • .codex
  • .config
  • .github
    Good: CI is configured (.github/workflows/archive.yml).
    Good: Issue or PR templates present.
  • .vida
  • crates
    Good: Test files detected (crates/docflow-cli/tests).
  • docs
  • install
  • scripts
  • spikes
  • tests
  • vida
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • AGENTS.changelog.jsonl
  • AGENTS.md
  • AGENTS.scaffold.changelog.jsonl
  • AGENTS.sidecar.changelog.jsonl
  • AGENTS.sidecar.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CODE_OF_CONDUCT.changelog.jsonl
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.changelog.jsonl
  • 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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LEAN-CTX.md
  • LICENSE
    Good: Licensed under MPL-2.0.
  • Makefile
  • README.changelog.jsonl
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    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.
  • README.md
  • SECURITY.changelog.jsonl
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.changelog.jsonl
  • SUPPORT.md
  • VERSION-PLAN.changelog.jsonl
  • VERSION-PLAN.md
  • vida.config.yaml
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/pomazanbohdan/vida-stack)](https://www.repo-grade.com/report/pomazanbohdan/vida-stack)

More graded Rust repos