86
/ 100
Well engineered for its size. A portfolio piece worth showing off.
All-in-one free/freemium/paid model providers for Pi
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 2Install and run instructions9pt
Add a section showing how to start or use the project.
- 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
80
README documents how to install the project.
README is present.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
87
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.
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (lint script in package.json).
Project health
97
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)
- 8Forks
- 6Releaseslatest 1mo ago
Community
- 57% - FairCommunity health
- -authors own >50% of commits
- 64Watchers
Responsiveness
- 12hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files26 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
- .pi
- docs
- lib
- provider-failover
- providers
- scripts
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .npmignore
- agents.md
- banner.jpg
- banner.png
- banner.svg
- CHANGELOG.md
- config.ts
- constants.ts
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.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.Good: Contributing guide includes code examples.
- index.ts
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- provider-helper.ts
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tsconfig.json
- vitest.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/apmantza/pi-free)