anti-slop
Opinionated Oxlint rules for rejecting low-evidence TypeScript and JavaScript patterns
Is anti-slop safe? Promising trust profile, but some evidence still deserves review.
Compare anti-slop
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: anti-slop scores 56.4/100 (Grade C), ranked #146 of 359 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 94% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How anti-slop could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.2 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +10.0 → 66.4 B · #51 of 359
How anti-slop compares in Agent Skills
- #144 Anti Slop 56.5 +0.1
- #145 Visual Explainer 56.5 +0.1
- #146 anti-slop 56.4 this agent
- #147 Open Managed Agents 56.2 −0.2
- #148 Aaron Marketing Skills 56.1 −0.3
Bars show each HVTrust score; the tick marks anti-slop’s 56.4.
Where the 56.4 comes from
HVTrust dimensions vs the Agent Skills average
56.4 / 100 · 100.0% confidenceanti-slop Agent Skills average (359 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
66.4 / 100Supply Chain Trust
Common questions about anti-slop
Does anti-slop publish package provenance?
Does anti-slop have an OpenSSF Scorecard?
Is anti-slop actively maintained?
What license does anti-slop use?
Are anti-slop's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain anti-slop?
For maintainers
HVTrust scores anti-slop from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/dmmulroy-anti-slop)
<a href="https://hvtracker.net/agents/dmmulroy-anti-slop"><img src="https://hvtracker.net/badge/dmmulroy-anti-slop.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON