92
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Simple, but flexible HTTP client library, with support for multiple backends.
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 .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
88
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
91
Test files detected (bin/test).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Ruby linting configured (.editorconfig).
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
- 4 / 9Commits (30d / 90d)
- 1,021Forks
- 114Releaseslatest 12y ago
Community
- 87% - GoodCommunity health
- 3 bus factorauthors own >50% of commits
- 5,944Watchers
Responsiveness
- 5hMedian issue response
- 22hMedian PR merge time
- 59Open issues
Repository files26 root entries
- .ai
- .claude
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 3 ecosystems (bundler, github-actions, npm). Dependencies stay current.Good: Issue or PR templates present.
- binGood: Test files detected (bin/test).
- config
- docs
- examples
- lib
- spec
- .cursorrules
- .editorconfigGood: Ruby linting configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .rspec
- .rubocop_todo.yml
- .rubocop.yml
- .yardopts
- CHANGELOG.md
- faraday.gemspec
- GemfileGood: Dependency manifest found (Gemfile).
- LICENSE.mdGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.json
- 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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- UPGRADING.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/lostisland/faraday)