{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-DEPENDENCY-GRAPH-BUILD-VARIABLE-OMISSION-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub: Static dependency analysis cannot resolve build variables",
  "system": "GitHub",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Will GitHub dependency graph include packages whose names or versions are supplied through build variables?",
  "near_questions": [
    "Why is a variable-defined dependency missing from GitHub graph?",
    "Can static analysis read our build-time package version?",
    "Which build-resolved dependencies need separate inventory evidence?",
    "Does a manifest parse prove the graph includes every package?",
    "What should be compared between the build and dependency graph?",
    "Can a missing dependency explain absent vulnerability alerts?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub states that manifest analysis lacks the project build environment and cannot resolve variables used for dependency names or versions. Such dependencies are not automatically included through that analysis. A graph review must reconcile build-resolved inputs before claiming inventory completeness.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Actual scan completeness or a vulnerability-free assessment",
    "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 states that manifest analysis lacks the project build environment and cannot resolve variables used for dependency names or versions. Such dependencies are not automatically included through that analysis. A graph review must reconcile build-resolved inputs before claiming inventory completeness.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub dependency graph troubleshooting",
    "source_url": "https://docs.github.com/en/code-security/reference/supply-chain-security/troubleshoot-dependabot/dependency-graph-errors",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-DEPENDENCY-GRAPH-BUILD-VARIABLE-OMISSION-01-v1",
    "candidate_record_sha256": "9dacff6690e9e92857a620ff3493b830bdc771b4979bb0132ca93a7531388723",
    "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 states that manifest analysis lacks the project build environment and cannot resolve variables used for dependency names or versions. Such dependencies are not automatically included through that analysis. A graph review must reconcile build-resolved inputs before claiming inventory completeness.",
    "required_buyer_context": "The manifest and variable-based declarations. The build-resolved names, versions and lock information. The graph or submitted snapshot used for comparison. 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": "Will GitHub dependency graph include packages whose names or versions are supplied through build variables?",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub states that manifest analysis lacks the project build environment and cannot resolve variables used for dependency names or versions. Such dependencies are not automatically included through that analysis. A graph review must reconcile build-resolved inputs before claiming inventory completeness.",
      "source_ids": [
        "github-graph"
      ]
    },
    "buyer_evidence_required": [
      "The manifest and variable-based declarations.",
      "The build-resolved names, versions and lock information.",
      "The graph or submitted snapshot used for comparison."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim complete dependency coverage while unresolved build variables omit required packages."
    },
    "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-graph",
        "url": "https://docs.github.com/en/code-security/reference/supply-chain-security/troubleshoot-dependabot/dependency-graph-errors",
        "final_url": "https://docs.github.com/en/code-security/reference/supply-chain-security/troubleshoot-dependabot/dependency-graph-errors",
        "title": "GitHub dependency graph troubleshooting",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:02:03.253Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "f701d6b3ea2a1f8ce6acad7eb8c1a4b6ec7e059d9b43fe38945596682c2aecbc",
        "bytes": 584550,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Will GitHub dependency graph include packages whose names or versions are supplied through build variables?"
        ]
      }
    ],
    "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 buyer needs to know whether the graph covers the dependencies actually selected by the build.",
      "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 variable-based declarations. The build-resolved names, versions and lock information. The graph or submitted snapshot used for comparison."
    },
    "buyer_relevance": "A software buyer needs to know whether the graph covers the dependencies actually selected by the build.",
    "refusal_conditions": [
      "Do not claim complete dependency coverage while unresolved build variables omit required packages."
    ]
  },
  "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 buyer needs to know whether the graph covers the dependencies actually selected by the build.",
    "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-graph-build-variable-omission",
  "machine_readable_record": "/varexis-index/records/github-dependency-graph-build-variable-omission.json"
}
