Package Security
Known vulnerabilities for package+version; normalized evidence, not a safety verdict.
Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.
$0.003 / callPOST /package/securityx402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- check a specific npm or PyPI package version for known vulnerabilities in OSV
- find known CVEs and security advisories affecting a dependency version
- preflight dependency vulnerability evidence before installing or upgrading a package
What Forest guarantees
- bounded normalized public-source lookup
Boundaries
- provider-specific guarantees
- unpublished facts
Machine contract
The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.
Input example
{
"ecosystem": "npm",
"package": "express",
"version": "4.21.2"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/package/security
Related capabilities
- Package License — Normalize declared package license metadata toward SPDX; no legal compatibility conclusion.
- Package Changed — Detect whether normalized public npm or PyPI package registry state changed since a saved fingerprint. Returns a deterministic SHA-256 fingerprint for package/version existence, latest/resolved version, deprecation or yank state, license and runtime requirement. No dependency graph, vulnerability scan or registry mutation.
- Package Preflight — Verify whether a specific npm or PyPI package version exists before installation, resolve the current/latest version, and report deprecation or yank state when available, plus license and runtime requirement. This is a public-registry package install preflight; it does not resolve dependency graphs or perform vulnerability analysis.