{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T01:25:58.088Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-PUSH-BYPASS-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub push protection: Exceptions and reviewer authority",
  "system": "GitHub push protection",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does enabled push protection prove no secret can be pushed?",
  "near_questions": [
    "Does push protection guarantee a repository contains no secrets?",
    "Who can approve a blocked secret push?",
    "Can contributors bypass without delegated review?",
    "What evidence shows exception oversight is active?",
    "Can a GitHub App review bypass requests?",
    "Does a successful push prove no secret was detected?",
    "Which roles have direct bypass privileges?",
    "What should procurement request about secret-scanning exceptions?",
    "Can an approved exception still contain sensitive material?",
    "How should an agent qualify a no-secret claim?",
    "Can I save the reviewed push-protection boundary?",
    "When should bypass authority be reviewed again?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub documents bypass paths. With delegated bypass, contributors without bypass privileges need reviewer approval; without it, contributors can bypass at their discretion. Review exception permissions and decisions before interpreting the feature as a no-secret guarantee.",
      "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 documents bypass paths. With delegated bypass, contributors without bypass privileges need reviewer approval; without it, contributors can bypass at their discretion. Review exception permissions and decisions before interpreting the feature as a no-secret guarantee.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-GITLAB-MASKING-01-v1",
    "VXI-EXT-PROCUREMENT-SLACK-SCIM-DEACTIVATION-01-v1",
    "VXI-EXT-PROCUREMENT-GCP-KEY-LIFECYCLE-01-v1",
    "VXI-EXT-PROCUREMENT-AWS-LAST-ACCESS-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub push protection bypass review",
    "source_url": "https://docs.github.com/en/code-security/concepts/secret-security/bypass-requests",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-PUSH-BYPASS-01-v1",
    "candidate_record_sha256": "d21af19b598fd733dee86cbd944708a4731afb2c464ef2321795591dee77f118",
    "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 documents bypass paths. With delegated bypass, contributors without bypass privileges need reviewer approval; without it, contributors can bypass at their discretion. Review exception permissions and decisions before interpreting the feature as a no-secret guarantee.",
    "required_buyer_context": "Repository, delegated-bypass configuration, privileged roles and review period.",
    "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": "Push protection prevents every secret-containing push.",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub documents bypass paths. With delegated bypass, contributors without bypass privileges need reviewer approval; without it, contributors can bypass at their discretion. Review exception permissions and decisions before interpreting the feature as a no-secret guarantee.",
      "source_ids": [
        "github-bypass"
      ]
    },
    "buyer_evidence_required": [
      "Effective bypass configuration and privileged identities",
      "Designated human or app reviewers and their authority",
      "Exception decisions for the relevant repository and period"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not accept an absolute prevention claim from enablement alone."
    },
    "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-bypass",
        "url": "https://docs.github.com/en/code-security/concepts/secret-security/bypass-requests",
        "final_url": "https://docs.github.com/en/code-security/concepts/secret-security/bypass-requests",
        "title": "GitHub push protection bypass review",
        "checked_on": "2026-10-14",
        "sha256": "1148662f12802ee7b0bec0992f4030bda4c2ecd9d6885290dd76471e304949c2",
        "bytes": 558804
      }
    ],
    "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": "Preserve the exception checks used in a source-control procurement 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 reviewer permissions, bypass policy and app approvals."
    }
  },
  "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-push-protection-bypass-evidence",
  "machine_readable_record": "/varexis-index/records/github-push-protection-bypass-evidence.json"
}