Response Field Reference

Whether attestd has coverage data for this product. If false, CVE risk fields are absent. The response may still include a typosquat object when the requested name fails package name integrity.

Deterministic risk classification for the queried version. Values in severity order from highest to lowest:

When multiple CVE version ranges match the queried version, the highest severity across all matching ranges is returned. See multi-range aggregation.

The reasons behind the risk_state classification. An empty array means no relevant risk factors were identified (typical for none).

internet_exposed_service is derived from CVE properties (remote_exploitable and authentication_required = false). It does not indicate Attestd has verified the service is reachable from the internet.

Whether any CVE affecting this version is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. KEV membership means exploitation has been observed in the wild.

When multiple version ranges match: true if any matching range has an actively-exploited CVE.

Whether the vulnerability can be exploited over a network without requiring local access to the target host.

When multiple version ranges match: true if any matching range has a remotely-exploitable CVE.

Whether exploitation requires valid credentials on the target system. false means at least one CVE has an unauthenticated attack path.

Whether a fixed version is available for this product. true means upgrading to fixed_version resolves all known risks in the queried version.

The earliest version that resolves all CVEs affecting the queried version. null if no patch is available or the product has no known affected CVEs (risk_state: "none").

Signal confidence score reflecting the quality and corroboration of the underlying data.

When multiple version ranges match: the minimum confidence across all matching rows is returned. A low-confidence result on any range lowers the overall confidence score.

For a full explanation of what drives each confidence tier and how the LLM extraction pipeline works, see Why Attestd: confidence score semantics.

The CVE identifiers that contributed to this risk assessment. Empty for risk_state: "none".

When multiple version ranges match, this is the union of all CVE IDs across all matching rows.

The highest EPSS probability score across all CVEs affecting this version. CVSS measures severity. KEV records confirmed exploitation. EPSS predicts exploitation probability in the next 30 days.

null when no matching CVE has an EPSS score yet (very new CVEs or product with no CVEs). Aggregation: max across all CVE IDs in the version range.

Per-CVE detail records. Present only when include=cves is passed on the request. null on the default response. Each entry corresponds to one ID in cve_ids.

Sub-fields:

Example response with include=cves:

{
  "product": "log4j",
  "version": "2.14.1",
  "supported": true,
  "risk_state": "critical",
  "risk_factors": [
    "active_exploitation",
    "remote_code_execution",
    "no_authentication_required",
    "internet_exposed_service",
    "patch_available"
  ],
  "actively_exploited": true,
  "remote_exploitable": true,
  "authentication_required": false,
  "patch_available": true,
  "fixed_version": "2.25.4",
  "confidence": 0.5,
  "cve_ids": ["CVE-2021-44228", "CVE-2021-45046", "CVE-2021-45105"],
  "max_epss": 0.99999,
  "cves": [
    {
      "cve_id": "CVE-2021-44228",
      "cvss_score": 10.0,
      "actively_exploited": true,
      "remote_exploitable": true,
      "epss_score": 0.99999,
      "epss_percentile": 1.0
    },
    {
      "cve_id": "CVE-2021-45046",
      "cvss_score": 9.0,
      "actively_exploited": true,
      "remote_exploitable": true,
      "epss_score": 0.97123,
      "epss_percentile": 0.998
    }
  ],
  "last_updated": "2026-07-08T10:58:13.230818Z",
  "supply_chain": null,
  "typosquat": null
}

The UTC timestamp of the most recent synthesis run that produced this result. Pairs with the X-Attestd-Knowledge-Age response header.

When multiple version ranges match: the most recent timestamp across all matching rows.

Supply chain integrity data for monitored PyPI and npm packages. null for CVE-only products (nginx, PostgreSQL, etc.). See Supply Chain Integrity for the full monitored package list.

Sub-fields:

Example PyPI response with supply chain data:

{
  "product": "litellm",
  "version": "1.82.7",
  "supported": true,
  "risk_state": "none",
  "risk_factors": [],
  "actively_exploited": false,
  "remote_exploitable": false,
  "authentication_required": false,
  "patch_available": false,
  "fixed_version": null,
  "confidence": 1,
  "cve_ids": [],
  "cves": null,
  "max_epss": null,
  "supply_chain": {
    "compromised": true,
    "sources": [
      "osv",
      "registry"
    ],
    "malware_type": "backdoor",
    "description": "TeamPCP supply chain attack: a malicious version contained a credential stealer in proxy_server.py targeting LLM provider API keys. Published at 10:39 UTC and removed within six hours after community detection.",
    "advisory_url": "https://docs.litellm.ai/blog/security-update-march-2026",
    "compromised_at": "2026-03-24T10:39:00Z",
    "removed_at": "2026-03-24T16:00:00Z"
  },
  "supply_chain_monitored": true,
  "typosquat": null,
  "last_updated": "2026-04-27T16:07:47.644177Z"
}

Package name integrity signal. Present when the requested name is a likely typosquat or an AI-hallucinated / conflated package name (slopsquatting). On unsupported products, this is the primary signal returned alongside supported: false. On supported supply-chain packages, it may appear alongside supply_chain when the requested name resembles another monitored package. null when no name-integrity issue is detected.

Sub-fields:

Example unsupported product with an AI-hallucinated package name detected:

{
  "supported": false,
  "typosquat": {
    "detected": true,
    "kind": "hallucination",
    "resembles": "jscodeshift",
    "likely_intended": ["jscodeshift"],
    "confidence": 0.9,
    "ecosystem": "npm"
  }
}