marcusquinn/aidevops
Grade a repo

0

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 12% of 5,156 graded repos

Vibe-Coding is easy. DevOps is hard. OpenCode & Git token-efficient AI agent automation for your app, business, and personal development. Opinionated tools, services, CLI & API stack for speed, security, and 24/7 results. Open-source first. SOTA everything. Try on your repos for money-making magic.

Documentation94
Engineering85
Health97
Shell271MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 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 a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

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

94

Contributing guide5pt77

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

85

CI/CD14pt57

CI is configured (.github/workflows/maintainer-gate-reusable.yml).

Reproducibility6pt80

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

Tests18pt100

Test files detected (.agents/plugins/opencode-aidevops/tests).

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt90

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)
  • 51
    Forks
  • 1000
    Releaseslatest 4mo ago

Community

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

Responsiveness

  • 6h
    Median issue response
  • <1h
    Median PR merge time
  • 8
    Open issues
Repository files66 root entries
  • _campaigns
  • _cases
  • _config
  • _feedback
  • _inbox
  • _knowledge
  • _performance
  • _projects
  • _reports
  • .agents
    Good: Test files detected (.agents/plugins/opencode-aidevops/tests).
    Good: Security policy present.
    Good: .gitignore present.
  • .claude-plugin
  • .github
    Good: CI is configured (.github/workflows/maintainer-gate-reusable.yml).
    Good: Issue or PR templates present.
  • .opencode
  • .qlty
  • .wiki
  • bin
  • configs
  • docs
  • homebrew
  • packages
  • scripts
  • templates
  • tests
    Good: Environment pinned via tests/docker/Dockerfile.
  • todo
  • .bandit
  • .codacy.yml
  • .codefactor.yml
  • .coderabbit.yaml
  • .gitattributes
  • .gitignore
  • .markdownlint-cli2.jsonc
  • .markdownlint.json
  • .markdownlintignore
  • .qltyignore
  • .repomixignore
  • .secretlintignore
  • .secretlintrc.json
  • .shellcheckrc
  • .task-counter
  • AGENT.md
  • AGENTS.md
  • aidevops.sh
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
  • CREDITS.md
  • DESIGN.md
  • LICENSE
    Good: Licensed under MIT.
  • MODELS-PERFORMANCE.md
  • MODELS.md
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
  • repomix-instruction.md
  • repomix.config.json
  • requirements-lock.txt
  • requirements.txt
  • SECURITY.md
  • setup.sh
  • sonar-project.properties
  • TERMS.md
  • TODO.md
  • tsconfig.json
  • VERSION
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/marcusquinn/aidevops)](https://www.repo-grade.com/report/marcusquinn/aidevops)

More graded Shell repos