0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Known filters subscriptions transformed for better compatibility with AdGuard
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
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
70
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.
This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.
README documents how to install the project.
Licensed under LGPL-3.0.
Engineering
80
No dependency lockfile found (−70 pts).
→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.
CI is configured (.github/workflows/build-3p.yaml).
Test script and framework are configured in package.json.
Linter or formatter configured (.eslintrc.cjs).
Issue or PR templates present.
Project health
94
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)
- 71Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 348Watchers
Responsiveness
- 1d 1hMedian issue response
- <1hMedian PR merge time
- 13Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/build-3p.yaml).Good: Issue or PR templates present.
- filters
- groups
- locales
- platforms
- .eslintignore
- .eslintrc.cjsGood: Linter or formatter configured (.eslintrc.cjs).
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- .markdownlintignore
- AGENTS.md
- DEVELOPMENT.md
- LICENSEGood: Licensed under LGPL-3.0.
- optimization_config.json
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.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.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/adguardteam/filtersregistry)