{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-DEPENDENCY-SUBMISSION-SOURCE-PRECEDENCE-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub: Dependency submissions have source precedence",
  "system": "GitHub",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does enabling automatic dependency submission replace a user-submitted manifest snapshot in GitHub graph?",
  "near_questions": [
    "Which dependency submission takes priority in GitHub graph?",
    "Can a manual snapshot outrank automatic dependency submission?",
    "Do Dependabot graph jobs outrank static manifest analysis?",
    "What detector and correlator evidence identifies the displayed inventory?",
    "Does enabling automation prove graph freshness?",
    "Can multiple collection methods produce one chosen manifest view?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub describes one displayed manifest instance selected through source precedence: user submissions outrank Dependabot graph jobs, automatic submissions and static analysis. Same-detector correlators can be merged. Enabling automation therefore does not establish that its snapshot is the evidence currently displayed.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Independent validation of submitted dependencies or automatic correction of stale snapshots",
    "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": "GitHub describes one displayed manifest instance selected through source precedence: user submissions outrank Dependabot graph jobs, automatic submissions and static analysis. Same-detector correlators can be merged. Enabling automation therefore does not establish that its snapshot is the evidence currently displayed.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub dependency graph data sources",
    "source_url": "https://docs.github.com/en/code-security/concepts/supply-chain-security/dependency-graph-data",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-DEPENDENCY-SUBMISSION-SOURCE-PRECEDENCE-01-v1",
    "candidate_record_sha256": "2874af2534bfe8f26af97905975eaaac54ef001031e12c6814c846dd7a3bcb6e",
    "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": "GitHub describes one displayed manifest instance selected through source precedence: user submissions outrank Dependabot graph jobs, automatic submissions and static analysis. Same-detector correlators can be merged. Enabling automation therefore does not establish that its snapshot is the evidence currently displayed.",
    "required_buyer_context": "The manifest and contributing submission methods. Detector, correlator and build revision metadata. The displayed dependency set and source precedence. 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": "Does enabling automatic dependency submission replace a user-submitted manifest snapshot in GitHub graph?",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub describes one displayed manifest instance selected through source precedence: user submissions outrank Dependabot graph jobs, automatic submissions and static analysis. Same-detector correlators can be merged. Enabling automation therefore does not establish that its snapshot is the evidence currently displayed.",
      "source_ids": [
        "github-priority"
      ]
    },
    "buyer_evidence_required": [
      "The manifest and contributing submission methods.",
      "Detector, correlator and build revision metadata.",
      "The displayed dependency set and source precedence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not assume the latest enabled collection method controls the graph without resolving higher-priority submissions."
    },
    "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": "github-priority",
        "url": "https://docs.github.com/en/code-security/concepts/supply-chain-security/dependency-graph-data",
        "final_url": "https://docs.github.com/en/code-security/concepts/supply-chain-security/dependency-graph-data",
        "title": "GitHub dependency graph data sources",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:02:03.929Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "9e7cdc00b39de8892e742c0f6aec050abf7eb0167f8105b7e2a0a5e6cde95ffb",
        "bytes": 581216,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does enabling automatic dependency submission replace a user-submitted manifest snapshot in GitHub graph?"
        ]
      }
    ],
    "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 build owner must identify which dependency submission actually supplies the graph before relying on its freshness and coverage.",
      "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 manifest and contributing submission methods. Detector, correlator and build revision metadata. The displayed dependency set and source precedence."
    },
    "buyer_relevance": "A build owner must identify which dependency submission actually supplies the graph before relying on its freshness and coverage.",
    "refusal_conditions": [
      "Do not assume the latest enabled collection method controls the graph without resolving higher-priority submissions."
    ]
  },
  "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 build owner must identify which dependency submission actually supplies the graph before relying on its freshness and coverage.",
    "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#github-dependency-submission-source-precedence",
  "machine_readable_record": "/varexis-index/records/github-dependency-submission-source-precedence.json"
}
