{ "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-16T14:13:51.913Z", "route_id": "agentic_pack_code_scanner_trust_v1", "question": "Code-scanner access and findings?", "answer": "Review access before connecting a scanner and interpret what its findings establish. Six dated documentation reviews compare SonarQube server filters and token scope, Snyk folder execution and ignore policies, and Semgrep invocation and scan exclusions. They preserve the evidence still needed before accepting a clean report or a claimed fix. They do not test your repository, credentials or deployment.", "records": [ { "record_id": "VXI-EXT-TOOL-TRUST-SONAR-01-v1", "url": "/varexis-index/records/sonarqube-mcp-read-only-filter-and-variant.json", "content_sha256": "f40cabfa1ad89482b70f2500edf6465d6f3620722a88708c53cbcdac57683b55", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-16T02:40:06.177Z", "record_id": "VXI-EXT-TOOL-TRUST-SONAR-01-v1", "record_kind": "external_reference", "title": "SonarQube MCP: Read-only filtering and deployment variants", "system": "SonarQube MCP Server", "evidence_family": "agent_tool_trust_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does connecting SonarQube MCP automatically restrict an agent to reading findings?", "near_questions": [ "Is SonarQube MCP read-only by default?", "Can an agent mark an issue accepted?", "Can per-request headers widen server permissions?", "How do tool-set and read-only filters interact?", "Which token identity is used by the server?", "Do hosted and local Sonar tools expose the same actions?", "Can local analysis require source-file access?", "Does a quality-gate result certify a release?", "Which entitlement controls advanced local tools?", "Can a buyer redistribute Sonar Results Data automatically?", "When should an agent refuse to change a finding?", "Can I save the reviewed Sonar configuration boundaries?" ], "supported_claims": [ { "claim": "The self-hosted server documents a read-only setting that disables write operations, but its default is false. Tool-set filters further narrow availability; per-request headers cannot widen server restrictions. Hosted and local variants differ, so a configuration review must bind the variant, identity and enabled tools rather than assume all connections are read-only.", "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 self-hosted server documents a read-only setting that disables write operations, but its default is false. Tool-set filters further narrow availability; per-request headers cannot widen server restrictions. Hosted and local variants differ, so a configuration review must bind the variant, identity and enabled tools rather than assume all connections are read-only.", "related_record_ids": [ "VXI-EXT-TOOL-TRUST-CHROME-DEVTOOLS-01-v1", "VXI-EXT-TOOL-TRUST-HF-01-v1", "VXI-EXT-TOOL-TRUST-JFROG-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "SonarSource MCP server repository", "source_url": "https://github.com/SonarSource/sonarqube-mcp-server", "checked_on": "2026-10-16", "candidate_record_id": "VXI-EXT-TOOL-TRUST-SONAR-01-v1", "candidate_record_sha256": "3f3d99ca45eff54445fb1c7c2821ca9a1629d57150deb3c3321b340c7a421c75", "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 self-hosted server documents a read-only setting that disables write operations, but its default is false. Tool-set filters further narrow availability; per-request headers cannot widen server restrictions. Hosted and local variants differ, so a configuration review must bind the variant, identity and enabled tools rather than assume all connections are read-only.", "required_buyer_context": "Server variant/version, token scope, filters, source mounts and intended use of results.", "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.", "trust_profile": { "schema": "varexis-agent-tool-trust/1", "identity": { "tool": "SonarQube MCP Server", "variant": "Publisher self-hosted server; hosted variants have different tool coverage" }, "review_status": "documentation_review_only", "checked_on": "2026-10-16", "version_scope": "Dated rolling documentation snapshot; no installed or hosted runtime version independently verified.", "plan_scope": "Buyer plan, entitlement and effective configuration are not verified.", "findings": [ { "field": "operator", "label": "Publisher and operator", "status": "documented", "statement": "SonarSource publishes the server; deployment may be local, self-hosted or publisher-hosted.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Retrieve code-quality context and perform supported analysis or finding operations.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Project, issue, metric, quality-gate and related information permitted to the identity.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "writes", "label": "Write capability", "status": "documented", "statement": "Issue and security-hotspot status changes are available unless filtered out.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "auth", "label": "Authentication", "status": "documented", "statement": "Local configuration uses a SonarQube token; HTTP examples use bearer credentials.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "permissions", "label": "Permission surface", "status": "documented", "statement": "Read-only and tool-set filters are cumulative; request headers only narrow server scope.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "review_inference", "statement": "Relevant source or analysis data can reach SonarQube and the client, depending on the selected tools.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "Variant differences, token scope and filesystem-dependent analysis can change exposure or availability.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Buyer configuration, entitlements, source mounts and Results Data usage rights are unverified.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "Require explicit authority before changing findings; do not treat internal-use Results Data terms as redistribution clearance.", "source_ids": [] } ], "evidence_sources": [ { "source_id": "sonar-repo", "url": "https://github.com/SonarSource/sonarqube-mcp-server", "final_url": "https://github.com/SonarSource/sonarqube-mcp-server", "title": "SonarSource MCP server repository", "checked_on": "2026-10-16", "sha256": "bfd4b9c4ededdbe9b76ef3323c67c5617b76ce99f09b3bec71d488fdb97a3c60", "bytes": 794444 }, { "source_id": "sonar-config", "url": "https://docs.sonarsource.com/sonarqube-mcp-server/build-and-configure", "final_url": "https://docs.sonarsource.com/sonarqube-mcp-server/setup", "title": "SonarQube MCP configuration", "checked_on": "2026-10-16", "sha256": "25fec80b9351472bc94eced3af4486cac91baa96dbb2985230066eca1a07e2a3", "bytes": 506577 }, { "source_id": "sonar", "url": "https://docs.sonarsource.com/sonarqube-mcp-server", "final_url": "https://docs.sonarsource.com/sonarqube-mcp-server", "title": "SonarQube MCP overview and data telemetry", "checked_on": "2026-10-16", "sha256": "406b7b3f7b83f57109889506ce9b9b291597f34aa8855c16e9aa93a890588a34", "bytes": 469375 } ], "observed_tool_execution": false, "policy_basis": "Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.", "commercial_reliance_boundary": "A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.", "paid_value": { "decision_context": "Save the exact restrictions needed to keep a review workflow read-only.", "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": "Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation.", "specific_watch": "Default filters, hosted coverage, analysis entitlements and result-use terms." }, "change_history": [ { "version": 1, "date": "2026-10-16", "change": "Initial documentation review; no earlier vendor assessment claimed." } ] }, "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#sonarqube-mcp-read-only-filter-and-variant", "machine_readable_record": "/varexis-index/records/sonarqube-mcp-read-only-filter-and-variant.json" } }, { "record_id": "VXI-EXT-PROCUREMENT-SONAR-TOKEN-SCOPE-01-v1", "url": "/varexis-index/records/sonarqube-token-type-and-effective-user-rights.json", "content_sha256": "cc609e45a6ff015b0da90a1a41347ac26f694c3cd2145ad8ce183b0bd3862109", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-16T14:13:51.913Z", "record_id": "VXI-EXT-PROCUREMENT-SONAR-TOKEN-SCOPE-01-v1", "record_kind": "external_reference", "title": "SonarQube tokens: Analysis scope and user authority", "system": "SonarQube Server", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does a SonarQube token used by a scanner have only analysis permissions?", "near_questions": [ "Is this a user or analysis token?", "Who issued the token?", "Does its author have admin rights?", "Which project does an analysis token cover?", "What happens when Execute Analysis is removed?", "Does connected mode accept this token type?", "Can the token invoke other Web API actions?", "Which permission evidence can be shared safely?", "Is its expiry recorded?", "Can the integration rotate its credential?", "Does scanner usage prove narrow rights?", "Can I save the token-scope assessment?" ], "supported_claims": [ { "claim": "User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.", "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": "User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "SonarQube: Managing tokens", "source_url": "https://docs.sonarsource.com/sonarqube-server/user-guide/managing-tokens", "checked_on": "2026-10-16", "candidate_record_id": "VXI-EXT-PROCUREMENT-SONAR-TOKEN-SCOPE-01-v1", "candidate_record_sha256": "22d00cf4ed742d53f1302d3c60a89eccc192a35e7f1893e91278a7455f1f059e", "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": "User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.", "required_buyer_context": "Client purpose, token type, issuing identity, project and effective grants. 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": "Every scanner integration token is restricted to one project.", "documented_statement": { "status": "documented", "statement": "User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.", "source_ids": [ "sonar-token" ] }, "buyer_evidence_required": [ "Token type and issuing identity, without the secret.", "Effective permissions and associated project.", "Client authentication requirements and revocation checks." ], "review_condition": { "status": "varexis_review_policy", "statement": "Inspect token type and effective grants before calling an integration least-privileged." }, "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": "sonar-token", "url": "https://docs.sonarsource.com/sonarqube-server/user-guide/managing-tokens", "final_url": "https://docs.sonarsource.com/sonarqube-server/user-guide/managing-tokens", "title": "SonarQube: Managing tokens", "checked_on": "2026-10-16", "sha256": "146b4cb9c96a1de2e9f9da5135e74da1150d2591b97db6cfd07d4210b5253f73", "bytes": 874408 } ], "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 credential-scope review without storing the credential.", "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": "Client purpose, token type, issuing identity, project and effective grants." } }, "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#sonarqube-token-type-and-effective-user-rights", "machine_readable_record": "/varexis-index/records/sonarqube-token-type-and-effective-user-rights.json" } }, { "record_id": "VXI-EXT-TOOL-TRUST-SNYK-01-v1", "url": "/varexis-index/records/snyk-mcp-folder-scan-execution-trust.json", "content_sha256": "7439827dfd12a4ffd1de6db75e6ddb4fb379d92c5062e04b0d9bddad95c5a45e", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-14T00:29:51.399Z", "record_id": "VXI-EXT-TOOL-TRUST-SNYK-01-v1", "record_kind": "external_reference", "title": "Snyk MCP: Folder trust and scan-time build execution", "system": "Snyk MCP", "evidence_family": "agent_tool_trust_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Can a Snyk dependency scan execute project tooling, even when the task is only a security review?", "near_questions": [ "Can a Snyk dependency scan run build tools?", "Does a security scan always avoid local code execution?", "What does Snyk folder trust establish?", "Which Snyk organization receives a scan?", "Can an MCP scan trigger authentication?", "What should I review before scanning an unfamiliar repository?", "Does a clean Snyk result establish deployment safety?", "Which project data leaves the local scan environment?", "Can an installed Snyk tool be skipped by an agent?", "What evidence supports permission to run dependency tooling?", "Can I retain the Snyk scan-execution boundary?", "When should an agent stop before scanning untrusted project code?" ], "supported_claims": [ { "claim": "Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.", "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": "Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.", "related_record_ids": [ "VXI-EXT-TOOL-TRUST-BROWSERBASE-01-v1", "VXI-EXT-TOOL-TRUST-N8N-01-v1", "VXI-EXT-TOOL-TRUST-SEMGREP-GUARDIAN-01-v1", "VXI-EXT-TOOL-TRUST-PAGERDUTY-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "Snyk MCP scanning, folder trust and ecosystem execution", "source_url": "https://github.com/snyk/studio-mcp", "checked_on": "2026-10-14", "candidate_record_id": "VXI-EXT-TOOL-TRUST-SNYK-01-v1", "candidate_record_sha256": "a469a68467f50d85c38edcec35e0f8cea4adf161c0ec84def0dfd1232baae391", "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": "Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.", "required_buyer_context": "Repository trust, scan type, ecosystem, CLI identity, organization and permitted local execution.", "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.", "trust_profile": { "schema": "varexis-agent-tool-trust/1", "identity": { "tool": "Snyk MCP", "variant": "Official Studio MCP and CLI-backed scanning" }, "review_status": "documentation_review_only", "checked_on": "2026-10-14", "version_scope": "Dated rolling documentation snapshot; no installed or hosted runtime version independently verified.", "plan_scope": "Buyer plan, entitlement and effective configuration are not verified.", "findings": [ { "field": "operator", "label": "Publisher and operator", "status": "documented", "statement": "Snyk publishes Studio MCP and the supporting CLI.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Scan code, dependencies, configuration and other supported artifact types.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Selected project contents, dependency information and scan results.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "writes", "label": "Write capability", "status": "documented", "statement": "Dependency scans may invoke third-party ecosystem tooling locally.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "auth", "label": "Authentication", "status": "documented", "statement": "CLI authentication supports OAuth and other documented token methods.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "permissions", "label": "Permission surface", "status": "documented", "statement": "Folder trust, selected scan and authenticated organization affect operation.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "review_inference", "statement": "Assess project information sent to Snyk and local tools for the chosen scan.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "Untrusted build tooling or the wrong organization can invalidate the intended scan boundary.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Repository behavior, effective trust settings and scan-product data flow are unverified.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "Require repository and execution-scope review before scans that invoke project tooling.", "source_ids": [] } ], "evidence_sources": [ { "source_id": "snyk-main", "url": "https://github.com/snyk/studio-mcp", "final_url": "https://github.com/snyk/studio-mcp", "title": "Snyk MCP scanning, folder trust and ecosystem execution", "checked_on": "2026-10-14", "sha256": "9232ecc44c18efcbd13b743e059fc3877a0270682fedd9c5efa01e6928810e99", "bytes": 276889 }, { "source_id": "snyk-auth", "url": "https://docs.snyk.io/developer-tools/snyk-cli/authenticate-to-use-the-cli", "final_url": "https://docs.snyk.io/developer-tools/snyk-cli/authenticate-to-use-the-cli", "title": "Snyk CLI authentication and account selection", "checked_on": "2026-10-14", "sha256": "d5ff4ada5324a6f2d616d4c34b6d635df914b888d744ae0dcb1017560aec9195", "bytes": 718966 } ], "observed_tool_execution": false, "policy_basis": "Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.", "commercial_reliance_boundary": "A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.", "paid_value": { "decision_context": "Keep the folder-trust and execution-context assumptions attached to a scan approval.", "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": "Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation.", "specific_watch": "Recheck scan type, build-tool behavior, folder trust and Snyk organization." }, "change_history": [ { "version": 1, "date": "2026-10-14", "change": "Initial documentation review; no earlier vendor assessment claimed." } ] }, "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-mcp-folder-scan-execution-trust", "machine_readable_record": "/varexis-index/records/snyk-mcp-folder-scan-execution-trust.json" } }, { "record_id": "VXI-EXT-PROCUREMENT-SNYK-IGNORE-SCOPE-01-v1", "url": "/varexis-index/records/snyk-ignore-scope-expiry-not-remediation.json", "content_sha256": "d92f2da4223f9458ae1f6e7a458feb44fb4defd8a5f458f0b527eed412b64107", "evidence": { "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" } }, { "record_id": "VXI-EXT-TOOL-TRUST-SEMGREP-GUARDIAN-01-v1", "url": "/varexis-index/records/semgrep-guardian-mcp-enforcement-trust.json", "content_sha256": "69714424c83f66742bec5aded48e2cfccdbe15f406e6bc14ad5a7d01f78b698b", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-14T00:29:51.399Z", "record_id": "VXI-EXT-TOOL-TRUST-SEMGREP-GUARDIAN-01-v1", "record_kind": "external_reference", "title": "Semgrep Guardian: Available scan tools and enforced checks", "system": "Semgrep Guardian MCP", "evidence_family": "agent_tool_trust_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does installing Semgrep MCP prove every agent code change was scanned?", "near_questions": [ "Does installing Semgrep MCP prove code was scanned?", "What distinguishes Semgrep MCP tools from hooks?", "Is the old standalone Semgrep MCP repository current?", "Which revision does a Semgrep scan result cover?", "Can an agent ignore an available scan tool?", "What evidence proves a required scan ran?", "Does an empty finding list certify secure code?", "Which Semgrep integration handles my code and findings?", "What should procurement ask about scanner enforcement?", "Can a scan of one revision support another revision?", "Can I save the Semgrep enforcement evidence boundary?", "When should an agent refuse to claim a completed security check?" ], "supported_claims": [ { "claim": "Semgrep distinguishes callable MCP scanning tools from event-triggered hooks. Tool availability alone does not prove invocation or coverage of a particular revision. Its former standalone MCP repository is archived and points to the main Semgrep distribution, so verify the installed integration and retain actual scan evidence.", "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": "Semgrep distinguishes callable MCP scanning tools from event-triggered hooks. Tool availability alone does not prove invocation or coverage of a particular revision. Its former standalone MCP repository is archived and points to the main Semgrep distribution, so verify the installed integration and retain actual scan evidence.", "related_record_ids": [ "VXI-EXT-TOOL-TRUST-BROWSERBASE-01-v1", "VXI-EXT-TOOL-TRUST-N8N-01-v1", "VXI-EXT-TOOL-TRUST-SNYK-01-v1", "VXI-EXT-TOOL-TRUST-PAGERDUTY-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "Semgrep Guardian MCP, hooks and scanning scope", "source_url": "https://semgrep.dev/products/semgrep-guardian/", "checked_on": "2026-10-14", "candidate_record_id": "VXI-EXT-TOOL-TRUST-SEMGREP-GUARDIAN-01-v1", "candidate_record_sha256": "637f2ad9a6d89522b21833bfeea94edb7d79c5572d8fe96c80d8d5e34195086b", "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": "Semgrep distinguishes callable MCP scanning tools from event-triggered hooks. Tool availability alone does not prove invocation or coverage of a particular revision. Its former standalone MCP repository is archived and points to the main Semgrep distribution, so verify the installed integration and retain actual scan evidence.", "required_buyer_context": "Installed distribution, enabled hooks, repository revision, scan scope, policy and result evidence.", "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.", "trust_profile": { "schema": "varexis-agent-tool-trust/1", "identity": { "tool": "Semgrep Guardian MCP", "variant": "Current Guardian integration; archived standalone server distinguished" }, "review_status": "documentation_review_only", "checked_on": "2026-10-14", "version_scope": "Dated rolling documentation snapshot; no installed or hosted runtime version independently verified.", "plan_scope": "Buyer plan, entitlement and effective configuration are not verified.", "findings": [ { "field": "operator", "label": "Publisher and operator", "status": "documented", "statement": "Semgrep publishes Guardian and the current Semgrep distribution.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Expose scanning capabilities to coding agents and support workflow checks.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Code or findings within the selected scan and integration scope.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "writes", "label": "Write capability", "status": "unknown", "statement": "Remediation or local file changes depend on the agent and configured workflow; not independently established.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "auth", "label": "Authentication", "status": "unknown", "statement": "The exact buyer authentication and account setup are not established by this review.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "permissions", "label": "Permission surface", "status": "unknown", "statement": "Effective local file access and organizational policy require configuration evidence.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "unknown", "statement": "Determine code, findings and telemetry recipients for the selected integration before use.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "A tool can be installed but never invoked, or scan a different revision.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Actual hooks, permissions, data flow and completed scan coverage remain unverified.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "Do not claim a revision was checked without a matching scan record and demonstrated trigger coverage.", "source_ids": [] } ], "evidence_sources": [ { "source_id": "semgrep-main", "url": "https://semgrep.dev/products/semgrep-guardian/", "final_url": "https://semgrep.dev/products/semgrep-guardian/", "title": "Semgrep Guardian MCP, hooks and scanning scope", "checked_on": "2026-10-14", "sha256": "4c300c56605930d16a796cfc4bc009470ebeef5a1e3ba77989fadfeaa1592e58", "bytes": 323896 }, { "source_id": "semgrep-hooks", "url": "https://semgrep.dev/blog/2026/mcp-vs-hooks-ai-agent-security/", "final_url": "https://semgrep.dev/blog/2026/mcp-vs-hooks-ai-agent-security/", "title": "Semgrep MCP tool availability and hook enforcement", "checked_on": "2026-10-14", "sha256": "79327edfd48d2f3b7f8ffa58fe843feecc5eff367183854cb0a3b3c579cdedd8", "bytes": 80221 }, { "source_id": "semgrep-migration", "url": "https://github.com/semgrep/mcp", "final_url": "https://github.com/semgrep/mcp", "title": "Semgrep archived MCP repository migration notice", "checked_on": "2026-10-14", "sha256": "7c93523605e2a21906eb6bb91809e734e02d70b08d00c7878a03675f27e00483", "bytes": 491439 } ], "observed_tool_execution": false, "policy_basis": "Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.", "commercial_reliance_boundary": "A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.", "paid_value": { "decision_context": "Preserve why scanner installation was insufficient evidence of a checked code revision.", "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": "Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation.", "specific_watch": "Recheck distribution migration, hook configuration, scan policy and retained results." }, "change_history": [ { "version": 1, "date": "2026-10-14", "change": "Initial documentation review; no earlier vendor assessment claimed." } ] }, "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#semgrep-guardian-mcp-enforcement-trust", "machine_readable_record": "/varexis-index/records/semgrep-guardian-mcp-enforcement-trust.json" } }, { "record_id": "VXI-EXT-PROCUREMENT-SEMGREP-IGNORE-COVERAGE-01-v1", "url": "/varexis-index/records/semgrep-exclusions-versus-ignored-finding-coverage.json", "content_sha256": "813375084c599bb9897ee1ca4aa34edba2ee1c7470ebbaa9d37305939b8805ee", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-16T14:13:51.913Z", "record_id": "VXI-EXT-PROCUREMENT-SEMGREP-IGNORE-COVERAGE-01-v1", "record_kind": "external_reference", "title": "Semgrep: Excluded files and ignored findings", "system": "Semgrep", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does an empty Semgrep findings list prove every relevant file was scanned?", "near_questions": [ "Which files were excluded?", "Were default ignore patterns applied?", "Was a finding generated then ignored?", "Does nosemgrep leave an ignored finding record?", "Which rules ran?", "Was the final revision scanned?", "Are binary files outside scope?", "Do size limits affect coverage?", "Does the UI filter ignored findings?", "What proves scan completion?", "What remains unassessed?", "Can I save the coverage review?" ], "supported_claims": [ { "claim": "File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.", "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": "File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "Semgrep: Ignore files, folders and code", "source_url": "https://docs.semgrep.dev/ignoring-files-folders-code", "checked_on": "2026-10-16", "candidate_record_id": "VXI-EXT-PROCUREMENT-SEMGREP-IGNORE-COVERAGE-01-v1", "candidate_record_sha256": "6694f07794bae7abb1f8c1047296452e7612a3af663e227606a7e7149d305a85", "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": "File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.", "required_buyer_context": "Revision, scan scope, ignore configuration, rules and finding states. 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": "No displayed findings establishes complete clean coverage.", "documented_statement": { "status": "documented", "statement": "File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.", "source_ids": [ "semgrep" ] }, "buyer_evidence_required": [ "Included and excluded paths for the exact revision.", "Applied ignore patterns and rule selection.", "Finding states and scan completion evidence." ], "review_condition": { "status": "varexis_review_policy", "statement": "Separate unscanned scope from ignored findings before accepting a clean-result claim." }, "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": "semgrep", "url": "https://docs.semgrep.dev/ignoring-files-folders-code", "final_url": "https://docs.semgrep.dev/ignoring-files-folders-code", "title": "Semgrep: Ignore files, folders and code", "checked_on": "2026-10-16", "sha256": "1d3d6b164c92cdef0d41485b6019430db4101e4b2cb9065c0eb318cd19ddc776", "bytes": 611668 } ], "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 scan-coverage and exception basis used in procurement.", "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": "Revision, scan scope, ignore configuration, rules and finding states." } }, "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#semgrep-exclusions-versus-ignored-finding-coverage", "machine_readable_record": "/varexis-index/records/semgrep-exclusions-versus-ignored-finding-coverage.json" } } ], "basis": "A frozen compilation of existing public documentation reviews and their source bindings. No new source review, tool execution, independent experiment or buyer assessment was performed for this package.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material. The saved pack is not continually refreshed. Hashes bind its contents; the optional delivery receipt is unsigned.", "pack": { "schema": "varexis-index-evidence-pack/1", "pack_id": "code-scanner-trust", "version": "1.0.0", "title": "Code-Scanner Trust — SonarQube, Snyk & Semgrep", "prepared_at_utc": "2026-10-16T14:43:10.371Z", "review_status": "documentation_review_only", "source_checked_on": [ "2026-10-14", "2026-10-16" ], "source_capture_date": null, "source_capture_boundary": "Existing dated review and upstream hash metadata are preserved. No new source bytes were acquired for this compilation; separate capture timestamps and independently tested runtime versions are not established.", "summary_markdown": "# Code-Scanner Trust — SonarQube, Snyk & Semgrep\n\nUse this pack to record the access and evidence questions behind a code-scanning workflow. Keep permission to inspect code, authority to execute project tooling and interpretation of findings separate. The three vendor pairs address different controls; this is not a ranking or proof of equivalent capabilities.\n\n## SonarQube MCP: Read-only filtering and deployment variants\nThe self-hosted server documents a read-only setting that disables write operations, but its default is false. Tool-set filters further narrow availability; per-request headers cannot widen server restrictions. Hosted and local variants differ, so a configuration review must bind the variant, identity and enabled tools rather than assume all connections are read-only.\n\nReviewed: 2026-10-16. Documentation review only.\n\nEvidence still needed: Buyer configuration, entitlements, source mounts and Results Data usage rights are unverified. Require explicit authority before changing findings; do not treat internal-use Results Data terms as redistribution clearance.\n\n## SonarQube tokens: Analysis scope and user authority\nUser tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.\n\nReviewed: 2026-10-16. Documentation review only.\n\nEvidence still needed: Token type and issuing identity, without the secret. Effective permissions and associated project. Client authentication requirements and revocation checks.\n\n## Snyk MCP: Folder trust and scan-time build execution\nSnyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.\n\nReviewed: 2026-10-14. Documentation review only.\n\nEvidence still needed: Repository behavior, effective trust settings and scan-product data flow are unverified. Require repository and execution-scope review before scans that invoke project tooling.\n\n## Snyk ignores: Scope and expiry are not remediation\nThe 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.\n\nReviewed: 2026-10-16. Documentation review only.\n\nEvidence still needed: Exact issue, scanner and policy file. Applicable paths, reason and parsed expiry. Separate evidence of a fix or accepted exception.\n\n## Semgrep Guardian: Available scan tools and enforced checks\nSemgrep distinguishes callable MCP scanning tools from event-triggered hooks. Tool availability alone does not prove invocation or coverage of a particular revision. Its former standalone MCP repository is archived and points to the main Semgrep distribution, so verify the installed integration and retain actual scan evidence.\n\nReviewed: 2026-10-14. Documentation review only.\n\nEvidence still needed: Actual hooks, permissions, data flow and completed scan coverage remain unverified. Do not claim a revision was checked without a matching scan record and demonstrated trigger coverage.\n\n## Semgrep: Excluded files and ignored findings\nFile or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.\n\nReviewed: 2026-10-16. Documentation review only.\n\nEvidence still needed: Included and excluded paths for the exact revision. Applied ignore patterns and rule selection. Finding states and scan completion evidence.\n\n## What payment adds\nThe entire pack is free to inspect or save locally. Single Request (GBP 5 plus applicable VAT) saves this complete version-bound JSON as one retrievable result. Evidence Receipt (GBP 19 plus applicable VAT) adds an unsigned delivery receipt. Eligible subscriptions use one query for the whole pack, not one per member. Keep the original access key and query reference for recovery; do not purchase again after uncertain payment.\n\n## Scope\nSource dates, documented claims, review considerations and unknowns remain distinct. No fresh investigation, buyer configuration test, certification, legal conclusion, continual refresh or permanent-retention commitment is included. Hashes bind content, not truth or independent assurance.\n", "comparison": [ { "record_id": "VXI-EXT-TOOL-TRUST-SONAR-01-v1", "tool": "SonarQube MCP Server", "review_status": "documentation_review_only", "checked_on": "2026-10-16", "findings": [ { "field": "operator", "label": "Publisher and operator", "status": "documented", "statement": "SonarSource publishes the server; deployment may be local, self-hosted or publisher-hosted.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Retrieve code-quality context and perform supported analysis or finding operations.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Project, issue, metric, quality-gate and related information permitted to the identity.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "writes", "label": "Write capability", "status": "documented", "statement": "Issue and security-hotspot status changes are available unless filtered out.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "auth", "label": "Authentication", "status": "documented", "statement": "Local configuration uses a SonarQube token; HTTP examples use bearer credentials.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "permissions", "label": "Permission surface", "status": "documented", "statement": "Read-only and tool-set filters are cumulative; request headers only narrow server scope.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "review_inference", "statement": "Relevant source or analysis data can reach SonarQube and the client, depending on the selected tools.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "Variant differences, token scope and filesystem-dependent analysis can change exposure or availability.", "source_ids": [ "sonar-repo", "sonar-config", "sonar" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Buyer configuration, entitlements, source mounts and Results Data usage rights are unverified.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "Require explicit authority before changing findings; do not treat internal-use Results Data terms as redistribution clearance.", "source_ids": [] } ] }, { "record_id": "VXI-EXT-PROCUREMENT-SONAR-TOKEN-SCOPE-01-v1", "subject": "SonarQube Server", "review_status": "documentation_review_only", "checked_on": "2026-10-16", "claim_to_check": "Every scanner integration token is restricted to one project.", "documented_statement": { "status": "documented", "statement": "User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.", "source_ids": [ "sonar-token" ] }, "buyer_evidence_required": [ "Token type and issuing identity, without the secret.", "Effective permissions and associated project.", "Client authentication requirements and revocation checks." ], "review_condition": { "status": "varexis_review_policy", "statement": "Inspect token type and effective grants before calling an integration least-privileged." }, "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." }, { "record_id": "VXI-EXT-TOOL-TRUST-SNYK-01-v1", "tool": "Snyk MCP", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "findings": [ { "field": "operator", "label": "Publisher and operator", "status": "documented", "statement": "Snyk publishes Studio MCP and the supporting CLI.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Scan code, dependencies, configuration and other supported artifact types.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Selected project contents, dependency information and scan results.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "writes", "label": "Write capability", "status": "documented", "statement": "Dependency scans may invoke third-party ecosystem tooling locally.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "auth", "label": "Authentication", "status": "documented", "statement": "CLI authentication supports OAuth and other documented token methods.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "permissions", "label": "Permission surface", "status": "documented", "statement": "Folder trust, selected scan and authenticated organization affect operation.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "review_inference", "statement": "Assess project information sent to Snyk and local tools for the chosen scan.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "Untrusted build tooling or the wrong organization can invalidate the intended scan boundary.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Repository behavior, effective trust settings and scan-product data flow are unverified.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "Require repository and execution-scope review before scans that invoke project tooling.", "source_ids": [] } ] }, { "record_id": "VXI-EXT-PROCUREMENT-SNYK-IGNORE-SCOPE-01-v1", "subject": "Snyk CLI", "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." }, { "record_id": "VXI-EXT-TOOL-TRUST-SEMGREP-GUARDIAN-01-v1", "tool": "Semgrep Guardian MCP", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "findings": [ { "field": "operator", "label": "Publisher and operator", "status": "documented", "statement": "Semgrep publishes Guardian and the current Semgrep distribution.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Expose scanning capabilities to coding agents and support workflow checks.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Code or findings within the selected scan and integration scope.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "writes", "label": "Write capability", "status": "unknown", "statement": "Remediation or local file changes depend on the agent and configured workflow; not independently established.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "auth", "label": "Authentication", "status": "unknown", "statement": "The exact buyer authentication and account setup are not established by this review.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "permissions", "label": "Permission surface", "status": "unknown", "statement": "Effective local file access and organizational policy require configuration evidence.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "unknown", "statement": "Determine code, findings and telemetry recipients for the selected integration before use.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "A tool can be installed but never invoked, or scan a different revision.", "source_ids": [ "semgrep-main", "semgrep-hooks", "semgrep-migration" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Actual hooks, permissions, data flow and completed scan coverage remain unverified.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "Do not claim a revision was checked without a matching scan record and demonstrated trigger coverage.", "source_ids": [] } ] }, { "record_id": "VXI-EXT-PROCUREMENT-SEMGREP-IGNORE-COVERAGE-01-v1", "subject": "Semgrep", "review_status": "documentation_review_only", "checked_on": "2026-10-16", "claim_to_check": "No displayed findings establishes complete clean coverage.", "documented_statement": { "status": "documented", "statement": "File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.", "source_ids": [ "semgrep" ] }, "buyer_evidence_required": [ "Included and excluded paths for the exact revision.", "Applied ignore patterns and rule selection.", "Finding states and scan completion evidence." ], "review_condition": { "status": "varexis_review_policy", "statement": "Separate unscanned scope from ignored findings before accepting a clean-result claim." }, "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." } ], "members": [ { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-16T14:13:51.913Z", "route_id": "agentic_reviewed_sonarqube_mcp_read_only_filter_and_variant", "question": "Does connecting SonarQube MCP automatically restrict an agent to reading findings?", "answer": "The self-hosted server documents a read-only setting that disables write operations, but its default is false. Tool-set filters further narrow availability; per-request headers cannot widen server restrictions. Hosted and local variants differ, so a configuration review must bind the variant, identity and enabled tools rather than assume all connections are read-only.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "d15e7b94fd3c2e8fc056f6abdd2be101f6158f2a1ff4d2100ae87c889913e795", "record_ids": [ "VXI-EXT-TOOL-TRUST-SONAR-01-v1" ] }, { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-16T14:13:51.913Z", "route_id": "agentic_reviewed_sonarqube_token_type_and_effective_user_rights", "question": "Does a SonarQube token used by a scanner have only analysis permissions?", "answer": "User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "639cb6e12d4b827b505b62a4efe5db7663af8fa4e51c947d17fc4c2a0fa90bad", "record_ids": [ "VXI-EXT-PROCUREMENT-SONAR-TOKEN-SCOPE-01-v1" ] }, { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-16T14:13:51.913Z", "route_id": "agentic_reviewed_snyk_mcp_folder_scan_execution_trust", "question": "Can a Snyk dependency scan execute project tooling, even when the task is only a security review?", "answer": "Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "63d347e27602490804b5b02a38e12f820bb7ff1de9c1fb12a95665f1e91ea102", "record_ids": [ "VXI-EXT-TOOL-TRUST-SNYK-01-v1" ] }, { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-16T14:13:51.913Z", "route_id": "agentic_reviewed_snyk_ignore_scope_expiry_not_remediation", "question": "Does a Snyk ignore rule establish that a vulnerability was fixed?", "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.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "879f2e472f665e5bf76a28ae638e5f707f8331219b19a87e1542cbb4a7b41fd2", "record_ids": [ "VXI-EXT-PROCUREMENT-SNYK-IGNORE-SCOPE-01-v1" ] }, { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-16T14:13:51.913Z", "route_id": "agentic_reviewed_semgrep_guardian_mcp_enforcement_trust", "question": "Does installing Semgrep MCP prove every agent code change was scanned?", "answer": "Semgrep distinguishes callable MCP scanning tools from event-triggered hooks. Tool availability alone does not prove invocation or coverage of a particular revision. Its former standalone MCP repository is archived and points to the main Semgrep distribution, so verify the installed integration and retain actual scan evidence.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "205909199c6d2dec99212892ce92307b3f1bc2f9043c9ac1933276281e0e97bd", "record_ids": [ "VXI-EXT-TOOL-TRUST-SEMGREP-GUARDIAN-01-v1" ] }, { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-16T14:13:51.913Z", "route_id": "agentic_reviewed_semgrep_exclusions_versus_ignored_finding_coverage", "question": "Does an empty Semgrep findings list prove every relevant file was scanned?", "answer": "File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "31b5f34fcf4fbf474df704f996a097485d32149b98654f50e49672148a63bac4", "record_ids": [ "VXI-EXT-PROCUREMENT-SEMGREP-IGNORE-COVERAGE-01-v1" ] } ], "rights_review": { "reviewed_on": "2026-10-16", "scope": "This exact public compilation of VAREXIS-authored review prose, factual identifiers, source links, dates and hashes.", "included": "Existing public VAREXIS review records and their limitations; an attributed comparison using the same documented findings.", "excluded": "Upstream documentation bodies, source code, screenshots, logos, private operator templates and protected evidence.", "redistribution_boundary": "Source links and hashes identify upstream material; they do not grant rights to redistribute that material. This package includes no upstream document bodies or code. Existing VAREXIS service terms apply to the supplied compilation.", "terms_url": "https://varexis.tech/checkout-terms", "independent_testing": false }, "delivery_unit": { "kind": "one_published_route", "member_count": 6, "developer_query_units": 1, "research_query_units": 1, "extra_member_purchases": false, "automatic_refresh": false } }, "snapshot_sha256": "3141c4a658f62ceabd16bc84d6f3260fdedea5c31595dd8344e7835431614f49" }