{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T13:19:39.838Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-JOB-TOKEN-PERMISSIONS-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub Actions: Job permissions and omitted scopes",
  "system": "GitHub Actions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a workflow permission declaration describe every job token without checking job overrides?",
  "near_questions": [
    "Which job ran?",
    "Was permission set globally?",
    "Is there a job override?",
    "Which scopes were omitted?",
    "Does write include read?",
    "What token defaults apply?",
    "Was this a fork trigger?",
    "Were write restrictions applied?",
    "Did the action use another token?",
    "Which workflow revision ran?",
    "Is the declaration job-specific?",
    "Can I save the job-permission review?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub supports workflow-level and job-level GITHUB_TOKEN permissions. When individual permissions are specified, omitted permissions become none. The job configuration and applicable default and trigger restrictions therefore matter when describing the token used by an action.",
      "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 supports workflow-level and job-level GITHUB_TOKEN permissions. When individual permissions are specified, omitted permissions become none. The job configuration and applicable default and trigger restrictions therefore matter when describing the token used by an action.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub: Workflow syntax for GitHub Actions",
    "source_url": "https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-JOB-TOKEN-PERMISSIONS-01-v1",
    "candidate_record_sha256": "a6e4e2cf61b49b4d7df7b6000886d44203afecfd581f2f9193337d20c1830e9c",
    "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 supports workflow-level and job-level GITHUB_TOKEN permissions. When individual permissions are specified, omitted permissions become none. The job configuration and applicable default and trigger restrictions therefore matter when describing the token used by an action.",
    "required_buyer_context": "Workflow revision, job, trigger and applicable token defaults. Effective buyer configuration and operational results were 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-17",
    "claim_to_check": "Does a workflow permission declaration describe every job token without checking job overrides?",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub supports workflow-level and job-level GITHUB_TOKEN permissions. When individual permissions are specified, omitted permissions become none. The job configuration and applicable default and trigger restrictions therefore matter when describing the token used by an action.",
      "source_ids": [
        "github-permissions"
      ]
    },
    "buyer_evidence_required": [
      "Workflow and job permission blocks.",
      "Repository defaults and trigger context.",
      "Credential type actually used by the action."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Review the executed job token separately from other credentials supplied to the workflow."
    },
    "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-permissions",
        "url": "https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax",
        "final_url": "https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax",
        "title": "GitHub: Workflow syntax for GitHub Actions",
        "checked_on": "2026-10-17",
        "sha256": "75ceb065df39204b3e29d842eababa0d9e7bd878c29d1654aaf39e4377e78a7e",
        "bytes": 2104874
      }
    ],
    "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": "Does a workflow permission declaration describe every job token without checking job overrides?",
      "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": "Workflow revision, job, trigger and applicable token defaults."
    }
  },
  "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-job-token-permissions-and-omitted-scopes",
  "machine_readable_record": "/varexis-index/records/github-job-token-permissions-and-omitted-scopes.json"
}
