71
/ 100
Solid engineering. The biggest lever is a reproducible setup.
Server automation framework and application
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4Install 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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
64
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
68
No dependency lockfile found (−70 pts).
→ Commit Gemfile.lock so Bundler installs are repeatable.
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.
Test files detected (acceptance/lib/puppet/acceptance/classifier_utils_spec.rb).
CI is configured (.github/workflows/checks.yaml).
Ruby linting configured (.rubocop.yml).
Project health
100
Dependency manifest found (Gemfile).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 0Commits (30d / 90d)
- 2,212Forks
- 12Releaseslatest 1y ago
Community
- 87% - GoodCommunity health
- 7 bus factorauthors own >50% of commits
- 7,915Watchers
Responsiveness
- 1d 1hMedian issue response
- 2hMedian PR merge time
- 98Open issues
Repository files34 root entries
- .githubGood: CI is configured (.github/workflows/checks.yaml).
- acceptanceGood: Test files detected (acceptance/lib/puppet/acceptance/classifier_utils_spec.rb).
- api
- benchmarks
- bin
- conf
- docs
- examples
- ext
- lib
- locales
- man
- rakelib
- references
- spec
- util
- yardoc
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .mailmap
- .noexec.yaml
- .rubocop_todo.yml
- .rubocop.ymlGood: Ruby linting configured (.rubocop.yml).
- .yardopts
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CODEOWNERS
- GemfileGood: Dependency manifest found (Gemfile).
- Guardfile.example
- install.rb
- LICENSEGood: Licensed under Apache-2.0.
- puppet.gemspec
- Rakefile
- README.mdGood: 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.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/puppetlabs/puppet)