{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T14:13:51.913Z",
  "record_id": "VXI-EXT-PROCUREMENT-SNYK-IGNORE-SCOPE-01-v1",
  "record_kind": "external_reference",
  "title": "Snyk ignores: Scope and expiry are not remediation",
  "system": "Snyk CLI",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Snyk ignore rule establish that a vulnerability was fixed?",
  "near_questions": [
    "Which issue was ignored?",
    "Does the ignore cover every path?",
    "Which scanner reads this policy?",
    "Is this a Snyk Code finding?",
    "Was the expiry parsed correctly?",
    "Can an invalid date make an ignore indefinite?",
    "Who accepted the exception?",
    "Does the reason identify a fix?",
    "What code revision contains remediation?",
    "Is the ignore still active?",
    "Does a clean report omit ignored issues?",
    "Can I retain the exception basis?"
  ],
  "supported_claims": [
    {
      "claim": "The ignore command changes policy treatment of an issue; it does not document a code fix. Paths and expiry determine scope. The .snyk issue-ignore mechanism is not supported for Snyk Code, which has a separate workflow. An invalid expiry can leave an ignore in place indefinitely, so inspect the effective policy.",
      "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": "The ignore command changes policy treatment of an issue; it does not document a code fix. Paths and expiry determine scope. The .snyk issue-ignore mechanism is not supported for Snyk Code, which has a separate workflow. An invalid expiry can leave an ignore in place indefinitely, so inspect the effective policy.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Snyk CLI: Ignore",
    "source_url": "https://docs.snyk.io/developer-tools/snyk-cli/commands/ignore",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SNYK-IGNORE-SCOPE-01-v1",
    "candidate_record_sha256": "7bb6c54121c071b23e5e98e51929bb06501a4a0aff866156586da9ef8517e241",
    "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": "The ignore command changes policy treatment of an issue; it does not document a code fix. Paths and expiry determine scope. The .snyk issue-ignore mechanism is not supported for Snyk Code, which has a separate workflow. An invalid expiry can leave an ignore in place indefinitely, so inspect the effective policy.",
    "required_buyer_context": "Scanner, issue ID, policy path, resource scope, expiry and fix evidence. Effective configuration and dated operational evidence have not been 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-16",
    "claim_to_check": "An ignored issue has been remediated.",
    "documented_statement": {
      "status": "documented",
      "statement": "The ignore command changes policy treatment of an issue; it does not document a code fix. Paths and expiry determine scope. The .snyk issue-ignore mechanism is not supported for Snyk Code, which has a separate workflow. An invalid expiry can leave an ignore in place indefinitely, so inspect the effective policy.",
      "source_ids": [
        "snyk-ignore"
      ]
    },
    "buyer_evidence_required": [
      "Exact issue, scanner and policy file.",
      "Applicable paths, reason and parsed expiry.",
      "Separate evidence of a fix or accepted exception."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not treat an ignore as remediation; require the scoped exception or fix evidence."
    },
    "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": "snyk-ignore",
        "url": "https://docs.snyk.io/developer-tools/snyk-cli/commands/ignore",
        "final_url": "https://docs.snyk.io/developer-tools/snyk-cli/commands/ignore",
        "title": "Snyk CLI: Ignore",
        "checked_on": "2026-10-16",
        "sha256": "c01d778ec674afa73d1ddce8c334e12e13c2166dd0c161ee5c42a22a535deb66",
        "bytes": 905326
      }
    ],
    "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 exception boundary used in a supplier vulnerability 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": "Scanner, issue ID, policy path, resource scope, expiry and fix evidence."
    }
  },
  "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#snyk-ignore-scope-expiry-not-remediation",
  "machine_readable_record": "/varexis-index/records/snyk-ignore-scope-expiry-not-remediation.json"
}