{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-TRIVY-OS-VENDOR-BACKPORT-DETECTION-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Trivy: Package origin affects advisory interpretation",
  "system": "Trivy",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an upstream fixed-version comparison replace Trivy OS-vendor advisory assessment?",
  "near_questions": [
    "Why can an older distro package contain a backported fix?",
    "Which advisory source does Trivy use for OS packages?",
    "Does comprehensive detection change false-positive tradeoffs?",
    "Can an upstream version number settle a distro finding?",
    "What package-origin evidence belongs in an exposure review?",
    "Could delayed vendor advisories leave detection gaps?"
  ],
  "supported_claims": [
    {
      "claim": "The captured Trivy v0.67 guide uses distribution advisories for OS-managed packages because vendors can backport fixes without adopting the upstream version. It also describes precision versus comprehensive detection tradeoffs. Package origin and advisory selection matter; an upstream version comparison alone can misstate exposure.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Exhaustive detection, malware assessment or confirmed exploitability",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
  ],
  "public_summary": "The captured Trivy v0.67 guide uses distribution advisories for OS-managed packages because vendors can backport fixes without adopting the upstream version. It also describes precision versus comprehensive detection tradeoffs. Package origin and advisory selection matter; an upstream version comparison alone can misstate exposure.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Trivy vulnerability scanning",
    "source_url": "https://trivy.dev/docs/latest/scanner/vulnerability/",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-TRIVY-OS-VENDOR-BACKPORT-DETECTION-BOUNDARY-01-v1",
    "candidate_record_sha256": "874db307f709241e92f5e7b46940ff2e33f2540dbab058773f6820734fbcce40",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "The captured Trivy v0.67 guide uses distribution advisories for OS-managed packages because vendors can backport fixes without adopting the upstream version. It also describes precision versus comprehensive detection tradeoffs. Package origin and advisory selection matter; an upstream version comparison alone can misstate exposure.",
    "required_buyer_context": "The installed package origin and distribution version. The selected advisory source and scanner mode. Vendor fix evidence and the exact package build. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-18",
    "claim_to_check": "Can an upstream fixed-version comparison replace Trivy OS-vendor advisory assessment?",
    "documented_statement": {
      "status": "documented",
      "statement": "The captured Trivy v0.67 guide uses distribution advisories for OS-managed packages because vendors can backport fixes without adopting the upstream version. It also describes precision versus comprehensive detection tradeoffs. Package origin and advisory selection matter; an upstream version comparison alone can misstate exposure.",
      "source_ids": [
        "trivy-vuln"
      ]
    },
    "buyer_evidence_required": [
      "The installed package origin and distribution version.",
      "The selected advisory source and scanner mode.",
      "Vendor fix evidence and the exact package build."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not declare a package affected or fixed solely from an upstream version when distribution backports are relevant."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "trivy-vuln",
        "url": "https://trivy.dev/docs/latest/scanner/vulnerability/",
        "final_url": "https://trivy.dev/docs/latest/scanner/vulnerability/",
        "title": "Trivy vulnerability scanning",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:02:03.531Z",
        "version_context": "Trivy documentation v0.67 (canonical version of captured page); check installed scanner version before applying",
        "sha256": "b05388625e9bb2ed774d8bdfeda04cdf61af782c2eaaa5db15253e471867a795",
        "bytes": 170565,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Can an upstream fixed-version comparison replace Trivy OS-vendor advisory assessment?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "A software reviewer must reconcile package provenance and vendor backports before accepting or disputing a vulnerability finding.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "The installed package origin and distribution version. The selected advisory source and scanner mode. Vendor fix evidence and the exact package build."
    },
    "buyer_relevance": "A software reviewer must reconcile package provenance and vendor backports before accepting or disputing a vulnerability finding.",
    "refusal_conditions": [
      "Do not declare a package affected or fixed solely from an upstream version when distribution backports are relevant."
    ]
  },
  "niche": {
    "niche_id": "dependency-advisory-reliance",
    "label": "Dependency & Advisory Reliance",
    "classification_id": "dependency",
    "classification_label": "Dependency/Advisory Reliance Boundaries",
    "topic_id": "dependency",
    "buyer_intent": "A software reviewer must reconcile package provenance and vendor backports before accepting or disputing a vulnerability finding.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#trivy-os-vendor-backport-detection-boundary",
  "machine_readable_record": "/varexis-index/records/trivy-os-vendor-backport-detection-boundary.json"
}
