97
/ 100
A top-tier open source project. Docs, tests, and CI are all in excellent shape.
Slim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)
Outstanding. A score of 97/100 puts this repo in a very small tier of truly well-engineered projects.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 2Contributing guide5pt
Add setup instructions, code style notes, and how to run tests.
- 3Contributing guide5pt
Show new contributors how to get a local dev environment running.
- 4Contributing guide5pt
Describe your linting/formatting rules and how to run them.
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
93
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.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
100
Test files detected (pkg/app/master/inspectors/image/extract_registry_test.go).
CI is configured (pkg/third_party/compose-go/.github/workflows/ci.yml).
Formatting enforced (vendor/github.com/Microsoft/go-winio/.golangci.yml).
Lockfile present (go.sum). Installs are reproducible.
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (go.mod).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 0Commits (30d / 90d)
- 833Forks
- 49Releaseslatest 7y ago
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 23,316Watchers
Responsiveness
- 1d 6hMedian issue response
- 11hMedian PR merge time
- 208Open issues
Repository files30 root entries
- .githubGood: Dependabot covers 2 ecosystems (github-actions, gitsubmodule). Dependencies stay current.Good: Issue or PR templates present.
- .vscode
- assets
- buildGood: Environment pinned via build/package/docker/Dockerfile.
- cmd
- examples
- pkgGood: Code of conduct present.Good: Test files detected (pkg/app/master/inspectors/image/extract_registry_test.go).Good: CI is configured (pkg/third_party/compose-go/.github/workflows/ci.yml).Issue: Build artifacts or local files may be committed (pkg/third_party/compose-go/cli/testdata/env-file/.env) (−40 pts).Fix: Remove them and add to .gitignore.
- scripts
- test
- vendorGood: Formatting enforced (vendor/github.com/Microsoft/go-winio/.golangci.yml).
- .deepsource.toml
- .dockerignore
- .gitignoreGood: .gitignore present.
- .gitmodules
- .gitpod.yml
- .markdownlint.json
- ADOPTERS.md
- CHANGELOG.md
- COMMUNITY_ACTIVITY_LOG.md
- CONTRIBUTING.mdIssue: 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.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- GOVERNANCE.md
- LICENSEGood: Licensed under Apache-2.0.
- MAINTAINERS.md
- Makefile
- 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.
- ROADMAP.md
- SECURITY.mdGood: Security policy present.
- WISHLIST.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/slimtoolkit/slim)