0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Open source container update monitoring — 23 registries, 20 notification triggers, audit log, OIDC auth, Prometheus metrics, and a modern dashboard.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
97
README documents how to install the project.
README is present.
Licensed under AGPL-3.0.
Contributing guide is detailed and thorough.
Engineering
74
Test files detected (.github/tests).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/ci-verify.yml).
Linter or formatter configured (biome.json).
Issue or PR templates present.
Project health
86
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 10Forks
- 74Releaseslatest 5mo ago
Community
- -Community health
- -authors own >50% of commits
- 203Watchers
Responsiveness
- 1hMedian issue response
- 1hMedian PR merge time
- 0Open issues
Repository files37 root entries
- .githubGood: Test files detected (.github/tests).Good: CI is configured (.github/workflows/ci-verify.yml).Good: Issue or PR templates present.
- .qlty
- app
- apps
- content
- docs
- e2e
- grafana
- scripts
- test
- ui
- .dockerignore
- .gitignoreGood: .gitignore present.
- .grype.yaml
- .markdownlint.json
- .node-version
- .nvmrc
- .yamllint.yml
- biome.jsonGood: Linter or formatter configured (biome.json).
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- codecov.yml
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- crowdin.yml
- DEPRECATIONS.md
- Docker.entrypoint.sh
- DockerfileGood: Environment pinned via Dockerfile.
- drydock.png
- healthcheck.c
- lefthook.yml
- LICENSEGood: Licensed under AGPL-3.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: 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.
- renovate.json
- SECURITY.mdGood: Security policy present.
- UPGRADE-NOTES.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/codeswhat/drydock)