CF Package Check

Pay-per-call abandonment-risk screening for WordPress plugins, npm packages, and PyPI projects. Queries WordPress.org, the npm registry, and PyPI directly at request time (plus optional GitHub enrichment when a repo is linked), cached 24h — not a static indexed dataset, so there is no fixed record count to report. Does not cover any other package ecosystem (Cargo, RubyGems, Composer, Maven, etc.). Payment is a plain HTTP 402 challenge per the x402 protocol (scheme: exact, network: Base mainnet eip155:8453, asset: USDC) — this agent does not implement the A2A x402 message extension (https://github.com/google-a2a/a2a-x402/v0.1); a client must speak raw HTTP x402, not A2A payment messages, to pay it.

Skills

• Package Abandonment Risk Check
  Is this WordPress plugin, npm package, or PyPI project abandoned? Query ecosystem (wordpress|npm|pypi) and name. $0.02 USDC per call via x402 (HTTP 402, not A2A payment messages). Returns status (active, stale, abandoned, deprecated, or closed), a 0-100 abandonment-risk score, months since the last update, the latest release, and the signals behind the score. Live-queried each call, cached 24h.
  softwaresupply-chainnpmpypiwordpress
• Full Package Abandonment Report
  Everything in package-check plus the score breakdown, raw registry facts, GitHub repository facts when a repo is linked, a version-history summary, support and issue stats, and a recommendation. $0.10 USDC per call via x402.
  softwaresupply-chainnpmpypiwordpressaudit

How to call

https://cf-package-check.cf-exclusion-check.workers.dev/v1/check

Listed in

Directories this entry was found in.