24
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
oisd blocklist
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 (65).
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
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.
- 3README12pt
Add an Overview, Install, Usage, and Contributing section at minimum.
- 4README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
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
26
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
README is present.
Licensed under GPL-3.0.
Engineering
12
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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 linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
Issue or PR templates present.
Project health
48
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 1289 / 4749Commits (30d / 90d)
- 15Forks
- 0Releases
Community
- 57% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 221Watchers
Responsiveness
- 5hMedian issue response
- -Median PR merge time
- 0Open issues
Repository files39 root entries
- .githubGood: Issue or PR templates present.
- abp_big.txt
- abp_nsfw_small.txt
- abp_nsfw.txt
- abp_small.txt
- dnsmasq_big.txt
- dnsmasq_nsfw_small.txt
- dnsmasq_nsfw.txt
- dnsmasq_small.txt
- dnsmasq2_big.txt
- dnsmasq2_nsfw_small.txt
- dnsmasq2_nsfw.txt
- dnsmasq2_small.txt
- domainswild_big.txt
- domainswild_nsfw_small.txt
- domainswild_nsfw.txt
- domainswild_small.txt
- domainswild2_big.txt
- domainswild2_nsfw_small.txt
- domainswild2_nsfw.txt
- domainswild2_small.txt
- LICENSEGood: Licensed under GPL-3.0.
- oisd_big.txt
- oisd_nsfw_small.txt
- oisd_nsfw.txt
- oisd_small.txt
- READMEGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- regex_big.txt
- regex_nsfw_small.txt
- regex_nsfw.txt
- regex_small.txt
- rpz_big.txt
- rpz_nsfw_small.txt
- rpz_nsfw.txt
- rpz_small.txt
- unbound_big.txt
- unbound_nsfw_small.txt
- unbound_nsfw.txt
- unbound_small.txt
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/sjhgvr/oisd)