Package License
Normalize declared package license metadata toward SPDX; no legal compatibility conclusion.
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.002 / callPOST /package/licensex402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- identify the declared npm or PyPI package license and normalized SPDX expression
- check package license metadata before adding a dependency
- find whether a dependency declares MIT Apache GPL or another software license
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": "pypi",
"package": "example"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/package/license
Related capabilities
- Package Security — Known vulnerabilities for package+version; normalized evidence, not a safety verdict.
- 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.