62
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Public datamining for all things Cloudflare
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 C (79).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
43
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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 is present.
A license file is present.
Engineering
60
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/mine-blog.yml).
Lockfile present (scripts/package-lock.json). Installs are reproducible.
Test files detected (data/middlecache/v1/cloudflare-skills/skills/turnstile-spin/templates/worker/test).
Linter or formatter configured (.editorconfig).
Project health
100
Dependency manifest found (data/api-schemas/_old/client/zone/firewall/waf/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
- 1 / 17Commits (30d / 90d)
- 27Forks
- 0Releases
Community
- 25% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 196Watchers
Responsiveness
- 2hMedian issue response
- <1hMedian PR merge time
- 25Open issues
Repository files8 root entries
- .githubGood: CI is configured (.github/workflows/mine-blog.yml).
- dataGood: A license file is present.Good: Test files detected (data/middlecache/v1/cloudflare-skills/skills/turnstile-spin/templates/worker/test).Good: Dependency manifest found (data/api-schemas/_old/client/zone/firewall/waf/package.json).
- scriptsGood: Lockfile present (scripts/package-lock.json). Installs are reproducible.
- site
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- 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.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/cloudflare-mining/cloudflare-datamining)