{
  "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"
}