Is an npm or PyPI package version safe and maintained
Is an npm or PyPI package version safe and maintained? Known vulnerabilities from OSV.dev (ids, CVEs, the advisory's own severity, fixed versions), deprecation or yank, licence, repository, publish dates, latest version, weekly downloads, dependency and maint…
by fiatdock.com · discovered, not yet claimed by its owner · updated 2026-10-13
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Is an npm or PyPI package version safe and maintained? Known vulnerabilities from OSV.dev (ids, CVEs, the advisory's own severity, fixed versions), deprecation or yank, licence, repository, publish dates, latest version, weekly downloads, dependency and maintainer counts, stated risk flags. No code scanning; unknowns are null. An unknown package or an outage is not charged. Pay-per-call via x402.
Tags: security · dependencies · npm · pypi · supply-chain · bazaar
Call contract
- Method
- POST
- Input
- json
- Output
- json
- Last paid call
- 2026-10-13
{
"ecosystem": "npm",
"name": "lodash",
"version": "4.17.20"
}{
"asOf": "2026-10-08T16:18:31.547Z",
"daysSinceLatestRelease": 189,
"dependencyCount": 0,
"deprecated": null,
"description": "Lodash modular utilities.",
"downloadsLastWeek": 203122461,
"ecosystem": "npm",
"homepage": "https://lodash.com/",
"isLatest": false,
"latestPublishedAt": "2026-04-01T21:01:20.458Z",
"latestVersion": "4.18.1",
"license": "MIT",
"maintainersCount": 1,
"name": "lodash",
"note": "Vulnerabilities are what OSV.dev lists for exactly lodash 4.17.20; none listed means none KNOWN to OSV, not that the code is safe. The same flaw published by two databases is one row; severity is the advisory's own label, never derived. Advisory data via OSV.dev; its sources include the GitHub Advisory Database and the PyPI Advisory Database (both CC-BY 4.0).",
"osvRecords": 5,
"publishedAt": "2020-08-13T16:53:54.152Z",
"repository": "https://github.com/lodash/lodash",
"riskFlags": [
"known_vulnerabilities",
"high_or_critical_vulnerability",
"newer_version_available"
],
"source": "npm registry (registry.npmjs.org) + npm download counts (api.npmjs.org) + OSV.dev",
"version": "4.17.20",
"vulnerabilities": [
{
"aliases": [
"CVE-2021-23337",
"CVE-2026-4800",
"GHSA-r5fr-rjxr-66jc"
],
"cvssVector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"fixedIn": [
"4.17.21"
],
"id": "GHSA-35jh-r3h4-6jhm",
"published": "2021-05-06T16:05:51.000Z",
"severity": "HIGH",
"summary": "Command Injection in lodash",
"url": "https://osv.dev/vulnerability/GHSA-35jh-r3h4-6jhm"
},
{
"aliases": [
"CVE-2021-23337",
"CVE-2026-4800",
"GHSA-35jh-r3h4-6jhm"
],
"cvssVector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"fixedIn": [
"4.18.0"
],
"id": "GHSA-r5fr-rjxr-66jc",
"published": "2026-04-01T23:51:12.000Z",
"severity": "HIGH",
"summary": "lodash vulnerable to Code Injection via `_.template` imports key names",
"url": "https://osv.dev/vulnerability/GHSA-r5fr-rjxr-66jc"
},
{
"aliases": [
"CVE-2020-28500"
],
"cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"fixedIn": [
"4.17.21"
],
"id": "GHSA-29mw-wpgm-hmr9",
"published": "2022-01-06T20:30:46.000Z",
"severity": "MODERATE",
"summary": "Regular Expression Denial of Service (ReDoS) in lodash",
"url": "https://osv.dev/vulnerability/GHSA-29mw-wpgm-hmr9"
},
{
"aliases": [
"CVE-2025-13465",
"CVE-2026-2950",
"GHSA-xxjr-mmjv-4gpg"
],
"cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L",
"fixedIn": [
"4.18.0"
],
"id": "GHSA-f23m-r3pf-42rh",
"published": "2026-04-01T23:50:27.000Z",
"severity": "MODERATE",
"summary": "lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`",
"url": "https://osv.dev/vulnerability/GHSA-f23m-r3pf-42rh"
},
{
"aliases": [
"CVE-2025-13465",
"CVE-2026-2950",
"GHSA-f23m-r3pf-42rh"
],
"cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L",
"fixedIn": [
"4.17.23"
],
"id": "GHSA-xxjr-mmjv-4gpg",
"published": "2026-01-21T23:01:22.000Z",
"severity": "MODERATE",
"summary": "Lodash has Prototype Pollution Vulnerability in `_.unset` and `_.omit` functions",
"url": "https://osv.dev/vulnerability/GHSA-xxjr-mmjv-4gpg"
}
],
"vulnerabilityCount": 5
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/30809.jsonfor the price and payment options. - Pay. Call
GET https://fiatdock.com/v1/dev/package. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.0027 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 3 calls · 2 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.0027 | 0xeB12bB2f52EeD33DBa6A00774E48324032Fd87C6 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xeB12bB2f52EeD33DBa6A00774E48324032Fd87C6",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "2700",
"amountUsd": 0.0027,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://fiatdock.com/v1/dev/package"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://fiatdock.com/v1/dev/package");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://fiatdock.com/v1/dev/package")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- fiatdock.com
- Endpoint
- https://fiatdock.com/v1/dev/package
- Machine-readable
/resources/30809.json