0
/ 100
Early-stage engineering. The fastest wins are CI and test coverage.
Open-source uptime monitoring SaaS — real-time website & API health checks, instant email alerts, public status pages. Free/Pro plans via Paystack (M-Pesa). Built with React, Node.js & PostgreSQL. Made in Kenya 🇰🇪
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (80).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4License6pt
Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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
57
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Engineering
32
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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 (artifacts/api-server/test).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Linter or formatter configured (devDependency in package.json).
Project health
89
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
- 2 / 2Commits (30d / 90d)
- 2Forks
- 0Releases
Community
- 28% - WeakCommunity health
- -authors own >50% of commits
- 2Watchers
Responsiveness
- 10d 9hMedian issue response
- -Median PR merge time
- 0Open issues
Repository files17 root entries
- artifactsGood: Test files detected (artifacts/api-server/test).
- lib
- screenshots
- scripts
- .env.example
- .gitignoreGood: .gitignore present.
- .npmrc
- deploy.sh
- ecosystem.config.cjs
- git-cleanup.sh
- LOCAL_DEV.md
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tsconfig.base.json
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/wolvarex/guardix)