Dependency Alerts Feed (JSON)
The shape a hosted dependency-alert API returns: alerts with lifecycle state, a nested advisory, a patched-version pointer and an explicitly null dismissed_reason on the alerts that were not dismissed. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.
{
"generated": "2026-01-01T00:00:00Z",
"repository": "orchard-example/gateway (fictional)",
"alerts": [
{
"number": 1,
"state": "open",
"dependency": {
"package": {
"ecosystem": "npm",
"name": "example-logger"
},
"manifest_path": "package-lock.json",
"scope": "runtime"
},
"security_advisory": {
"ghsa_id": "SAMPLE-ADVISORY-0001",
"summary": "SAMPLE advisory: fabricated improper-input-validation issue in a fictional logging library.",
"severity": "high",
"cve_id": "SAMPLE-CVE-2026-0001",
"identifiers": [
{
"type": "SAMPLE",
"value": "NOVUS-SAMPLE-2026-0001"
}
],
"cvss": {
"score": 8.1,
"vector_string": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
},
"cwes": [
{
"cwe_id": "CWE-20",
"name": "SAMPLE weakness class"
}
]
},
"security_vulnerability": {
"package": {
"ecosystem": "npm",
"name": "example-logger"
},
"severity": "high",
"vulnerable_version_range": "<3.5.0",
"first_patched_version": {
"identifier": "3.5.0"
}
},
"created_at": "2026-01-05T00:00:00Z",
"dismissed_reason": nullSpecifications
- Seed
- 51200
- Sample Only
- true
- Format
- alert feed
- Alerts
- 4
- States
- open, dismissed, fixed
- Nullable Fields
- dismissed_reason
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Consume an alert feed where optional fields are null rather than absent.
- Expected result
- Two open alerts, one dismissed with reason tolerable_risk and one fixed load correctly, and null dismissed_reason does not become the string 'None'.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Dependency Alerts Feed (JSON)” is a deterministic Novus Examples fixture for JSON parsing, API testing, Error handling. Flat, deeply nested, JSON Lines, and intentionally invalid JSON for testing parsers and error handling.
Documented properties for this file: seed 51200 · LF · alert feed. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
SBOM, lockfile, provenance, and advisory fixtures describe the same fabricated component tree across formats, so a converter or scanner can be diffed against a known answer. Every package name, version, hash, and advisory ID is invented — never treat a finding here as real.
Feed the file to your parser and assert it handles the documented quirks — quoted delimiters, embedded newlines, ragged rows, or invalid syntax; the valid↔invalid distinction is labelled in the title.
Code examples
import json
with open("dependency-alerts.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonGraphQL Error Response (JSON)GraphQL error response with message and location — negative case for GraphQL clients.
- jsonOSV Record With Schema Violations — Intentionally InvalidAn intentionally invalid OSV record: the JSON parses, but the required id is missing, modified is not an RFC 3339 timestamp, the SEMVER range has a fixed event with no introduced event, and severity.score is a number where the schema demands a CVSS vector string. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.
- jsonScanner Report, Truncated — Intentionally CorruptAn intentionally corrupt scanner report: a valid Trivy-shaped JSON document cut off inside the first finding, for testing that a CI gate fails the build rather than reporting zero vulnerabilities. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.
- jsonCycloneDX 1.6 Minimal SBOM (One Component)The smallest CycloneDX document that is still valid: required metadata, one fictional component, and no dependencies array — for testing that a reader handles an SBOM with nothing optional present. Every package, version, hash and licence is fictional — the tree describes nothing real.
- jsonCycloneDX SBOM With Schema Violations — Intentionally InvalidAn intentionally invalid CycloneDX SBOM: the JSON parses, but bomFormat is missing, one component has no name, and a dependency references a bom-ref that no component declares. Every package, version, hash and licence is fictional — the tree describes nothing real.
- jsonCycloneDX SBOM With Services and CompositionsA CycloneDX SBOM that declares external services and composition completeness alongside components — the sections tools most often skip. Both services are fictional endpoints on the .example domain. Every package, version, hash and licence is fictional — the tree describes nothing real.
Generated by generation/supply_chain.py. Free for any use, no attribution required — license.