{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-11T17:52:53.561Z",
  "record_id": "VXI-EXT-OSV-05-v1",
  "record_kind": "external_reference",
  "title": "OSV queries: Choose one package and version representation",
  "system": "OSV.dev",
  "evidence_family": "advisory_query_identity",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "How should an agent identify a package version in an OSV query?",
  "near_questions": [
    "How do I query OSV by package version?",
    "Can an OSV request combine commit and version?",
    "Why does a versioned package URL cause an OSV error?",
    "Should the version go in the purl or a separate field?",
    "Does OSV need the package ecosystem?",
    "Can I send both a purl and a package name?",
    "Are OSV query values case sensitive?",
    "How should an agent form a commit query?",
    "Does a successful OSV query confirm my installed package?",
    "Why can a package name alone be ambiguous?",
    "Which package identifier belongs in a vulnerability lookup?",
    "Does valid OSV input prove a package is safe?"
  ],
  "supported_claims": [
    {
      "claim": "OSV's query documentation separates commit queries from package-version queries. Do not combine a commit with a top-level version. Identify a package through its name and ecosystem, or through a package URL. Supply the version either separately or within that URL; supplying both returns a bad-request response. Preserve the actual package identity and case. A valid query does not establish that the identified package is deployed or safe.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "a valid query proving deployment or safety",
    "conflicting version fields silently resolved",
    "identical names across ecosystems treated as one package"
  ],
  "public_summary": "OSV's query documentation separates commit queries from package-version queries. Do not combine a commit with a top-level version. Identify a package through its name and ecosystem, or through a package URL. Supply the version either separately or within that URL; supplying both returns a bad-request response. Preserve the actual package identity and case. A valid query does not establish that the identified package is deployed or safe.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "OSV: POST /v1/query",
    "source_url": "https://google.github.io/osv.dev/post-v1-query/",
    "checked_on": "2026-10-11",
    "candidate_record_id": "VXI-EXT-OSV-05-v1",
    "candidate_record_sha256": "7bc243b3d6239f4f74ea726ce63620599349c82045b50ab59953aecfe6f458e6",
    "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": "OSV's query documentation separates commit queries from package-version queries. Do not combine a commit with a top-level version. Identify a package through its name and ecosystem, or through a package URL. Supply the version either separately or within that URL; supplying both returns a bad-request response. Preserve the actual package identity and case. A valid query does not establish that the identified package is deployed or safe.",
    "required_buyer_context": "Actual package identity, ecosystem and version or commit. This is a documentation review of upstream OSV input, not a live query or deployment assessment.",
    "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.",
  "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#osv-query-package-and-version-identity",
  "machine_readable_record": "/varexis-index/records/osv-query-package-and-version-identity.json"
}
