datastand.dev

Shares a payout wallet with 9 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

The latest npm security advisories, normalized for machines: severity, CVSS 3.x and 4.0 (score and vector, each null when upstream has not scored that version), affected packages, vulnerable ranges, patched versions, and a per-row `fix_status` (patched, partial or unpatched) so the advisories no upgrade can fix stand out without walking every affected package. Merged from two upstream orderings — the 100 most recently published advisories and the 100 most recently REVISED — so a CVSS score finally assigned, or a vulnerable range widened to include the version you run, reaches you instead of being invisible because the advisory was published weeks ago. Derived from the GitHub Advisory Database (CC-BY 4.0, attributed). Add ?since=<ISO-8601> to get only the advisories published or revised since your last fetch; if nothing has changed you are not charged, so polling for new vulnerabilities costs nothing until there are some. Every build carries a `coverage` block stating what it can and cannot answer: `delta_complete_since` is the point back to which a ?since= delta is complete — ask for one earlier and it is refused for free rather than served short — and `upstream_unchanged_since` says how long upstream has been serving the same newest advisory, because generated_at is the age of our fetch and not the age of the content. That block is on this free listing (info.output.example.coverage) at the current build's own figures, so you can check the bound against your polling interval before you pay for anything.