0
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
Aggregated AbuseIPDB blocklists with worst IPv4 & IPv6 offenders (~99% confidence)
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 D (64).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
48
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Engineering
16
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
No dependency lockfile found (−70 pts).
→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node 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.
CI is configured (.github/workflows/ci.yml).
Project health
86
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)
- 36Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 484Watchers
Responsiveness
- 2d 10hMedian issue response
- -Median PR merge time
- 1Open issues
Repository files21 root entries
- .cron
- .githubGood: CI is configured (.github/workflows/ci.yml).
- .vscode
- db
- stats
- .gitattributes
- .gitignoreGood: .gitignore present.
- abuseipdb-s100-120d.ipv4
- abuseipdb-s100-14d.ipv4
- abuseipdb-s100-180d.ipv4
- abuseipdb-s100-1d.ipv4
- abuseipdb-s100-30d.ipv4
- abuseipdb-s100-365d.ipv4
- abuseipdb-s100-3d.ipv4
- abuseipdb-s100-60d.ipv4
- abuseipdb-s100-7d.ipv4
- abuseipdb-s100-90d.ipv4
- abuseipdb-s100-all.ipv4.gz
- deno.json
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/borestad/blocklist-abuseipdb)