91
/ 100
A top-tier open source project. Docs, tests, and CI are all in excellent shape.
A library for generating fake data such as names, addresses, and phone numbers.
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
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
92
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
91
Test files detected (test).
Lockfile present (Gemfile.lock). Installs are reproducible.
CI is configured (.github/workflows/ruby.yml).
Ruby linting configured (.rubocop.yml).
Issue or PR templates present.
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 / 18Commits (30d / 90d)
- 3,162Forks
- 52Releaseslatest 6y ago
Community
- 75% - GoodCommunity health
- 6 bus factorauthors own >50% of commits
- 11,619Watchers
Responsiveness
- 13d 3hMedian issue response
- 31d 23hMedian PR merge time
- 35Open issues
Repository files24 root entries
- .githubGood: CI is configured (.github/workflows/ruby.yml).Good: Dependabot covers 2 ecosystems (bundler, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- benchmark
- bin
- custom-hooks
- doc
- experiments
- lib
- script
- tasks
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- .rubocop.ymlGood: Ruby linting configured (.rubocop.yml).
- .yardopts
- CHANGELOG.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.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.
- faker.gemspec
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- GENERATORS.md
- License.txtGood: Licensed under MIT.
- MAINTAINING.md
- Rakefile
- 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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/faker-ruby/faker)