{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T00:29:51.399Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-ACTIONS-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub Actions: Privileged workflows and untrusted contributions",
  "system": "GitHub Actions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a pull-request workflow prove external contributions cannot access privileged execution?",
  "near_questions": [
    "Does a pull-request workflow always run without secrets?",
    "Can a privileged workflow check out untrusted code?",
    "What GitHub Actions trigger ran this contribution check?",
    "Which token permissions were available to a workflow?",
    "Does a passing CI job prove isolation?",
    "Can self-hosted runner reuse affect contribution safety?",
    "What evidence supports a restricted CI execution claim?",
    "Does secret masking guarantee secrets never enter logs?",
    "Should procurement inspect workflow permissions or only the CI badge?",
    "How do I qualify an unverified CI isolation claim?",
    "Can I preserve the reviewed GitHub Actions privilege boundary?",
    "When does a changed workflow require a new supplier review?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub warns that privileged workflow triggers combined with untrusted checkout can expose secrets or repository write access. Review triggers, checked-out revisions and job permissions together. A pull-request label or successful workflow run does not establish an isolated execution boundary.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "GitHub warns that privileged workflow triggers combined with untrusted checkout can expose secrets or repository write access. Review triggers, checked-out revisions and job permissions together. A pull-request label or successful workflow run does not establish an isolated execution boundary.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-GITLAB-JOB-TOKEN-01-v1",
    "VXI-EXT-PROCUREMENT-DATADOG-INDEX-01-v1",
    "VXI-EXT-PROCUREMENT-ELASTIC-ROLES-01-v1",
    "VXI-EXT-PROCUREMENT-SENTRY-SCRUB-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub Actions privileged workflow and secret boundaries",
    "source_url": "https://docs.github.com/en/actions/reference/security/secure-use",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-ACTIONS-01-v1",
    "candidate_record_sha256": "82d1ba6ecf70d4ac2376b173cbfe292790940c447c40af92e80621fef1fa2e5b",
    "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 warns that privileged workflow triggers combined with untrusted checkout can expose secrets or repository write access. Review triggers, checked-out revisions and job permissions together. A pull-request label or successful workflow run does not establish an isolated execution boundary.",
    "required_buyer_context": "Workflow trigger, checked-out revision, job permissions, runner type and referenced secrets.",
    "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-14",
    "claim_to_check": "All contribution checks run without privileged access.",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub warns that privileged workflow triggers combined with untrusted checkout can expose secrets or repository write access. Review triggers, checked-out revisions and job permissions together. A pull-request label or successful workflow run does not establish an isolated execution boundary.",
      "source_ids": [
        "github-actions"
      ]
    },
    "buyer_evidence_required": [
      "Dated workflow definition and actual trigger",
      "Effective job token and secret access",
      "Evidence identifying the revision executed and runner isolation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require workflow evidence before accepting a blanket claim that contributor code cannot reach privileged execution."
    },
    "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-actions",
        "url": "https://docs.github.com/en/actions/reference/security/secure-use",
        "final_url": "https://docs.github.com/en/actions/reference/security/secure-use",
        "title": "GitHub Actions privileged workflow and secret boundaries",
        "checked_on": "2026-10-14",
        "sha256": "5a16e2df298a262fb898affed533d831c64ab0847dc2531126414242de5c68e6",
        "bytes": 466326
      }
    ],
    "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": "Save the privilege assumptions behind a supplier CI review.",
      "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": "Recheck workflow triggers, action revisions, runner placement and credential scope."
    }
  },
  "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-actions-privileged-workflow-check",
  "machine_readable_record": "/varexis-index/records/github-actions-privileged-workflow-check.json"
}