CF Package Check
https://packages.cfsoft.us/v1/checkPay-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.
Quality grade
How grading works- ✓ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✓ Payment address on record
- ✓ Settlement network declared
- ✓ Price declared
Paid endpoints
4 resource(s) advertised by this origin.
https://packages.cfsoft.us/v1/check
Is this WordPress plugin, npm package or PyPI project abandoned? Query ecosystem=wordpress|npm|pypi and name. 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.
https://packages.cfsoft.us/v1/report
Everything in /v1/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.
https://packages.cfsoft.us/v1/health
Upstream registry reachability and configuration. No payment required.
https://packages.cfsoft.us/.well-known/x402
This document. No payment required.
How to call
curl -X GET https://packages.cfsoft.us/v1/check
Listed in
Directories this entry was found in.