Skip to main content
The advisory API lets you discover security advisories for volumes hosted on a bibliotheca. You can list all advisories that affect a given volume or fetch a single advisory by its local ID. Advisory records follow a structured schema compatible with OSV-style range/event semantics. No authentication is required for read operations. Advisory write operations — create, update, withdrawal — are bibliotheca-local and not standardized in v0.1.

Endpoints

List advisories for a volume

string
Volume name (scopeless or @scope/name). Returns all advisories that affect the specified volume.

Fetch a single advisory

string
required
The bibliotheca-local advisory ID.

Advisory response fields

object
required
Advisory identifier object.
object
required
Source ecosystem information.
string
required
One of critical, high, medium, or low.
string
required
ISO 8601 timestamp when this advisory was first published.
string
required
ISO 8601 timestamp of the most recent update to this advisory.
object
Present when the advisory has been withdrawn.
object
required
Affected volume and version range information.
object[]
Advisory relationships for tracking supersession, related advisories, or duplicates.
string
Short human-readable summary of the advisory.
string
Full human-readable details about the vulnerability.

Example advisory

List response envelope

The list endpoint returns a collection envelope:

Affected version semantics

Affected version ranges use OSV-style event sequences. Read the events in order to determine which versions are affected:
  • introduced: "0" means affected from the beginning of version history
  • fixed: "1.4.0" means versions >= 0 and < 1.4.0 are affected
  • lastAffected: "1.3.9" means versions up to and including 1.3.9 are affected
Advisory targeting in v0.1 is volume-level only. Component-level impact metadata in componentImpact is informational and does not narrow or change the normative volume-level advisory target.
Scanner findings are not advisory records by themselves. A bibliotheca may create or update an advisory based on scanner information under local policy, but the portable contract is the advisory read and discovery model, not scanner-result interchange.