Source
Dependencies (SCA), licences & secrets — found from sitemap — SonarQube
Checked for SonarQube on 6 Nov 2026
- Page
- https://docs.sonarsource.com/sonarqube-cli/analysis/sca
- Checked
- 6 Nov 2026, 05:17 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:ee386febad040dffb3109b9a6797637eac440d65d08b83641bf90ddf1c93dcca
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Sca command Report an error
“sonar analyze dependency-risks runs SonarQube's Software Composition Analysis (SCA) against your local project's open-source dependencies and reports the risks found: vulnerabilities, malware, and prohibited licenses.”
-
Sca availability Report an error
“It's available on SonarQube Cloud (Advanced Security plan) and on SonarQube Server 2026.4 or newer (Advanced Security licensed).”
-
Pre commit hook Report an error
“Also enable the same scan on a pre-commit Git hook with sonar integrate git.”
-
Binaries download Report an error
“On first use, SonarQube CLI fetches the sca-scanner-cli and sonar-secrets binaries from binaries.sonarsource.com and caches them under ~/.sonar/sonarqube-cli/bin/.”
-
Secrets prescan Report an error
“Discovers dependency manifest and lock files under the project root and pre-scans them for hardcoded secrets. If secrets are found, the command aborts and lists each finding (file, line, and masked secret).”
-
Block threshold Report an error
“It blocks the commit when any scanned project has new (NEW) risks at MEDIUM severity or above (BLOCKER, HIGH, and MEDIUM).”
-
Source code privacy Report an error
“SonarQube CLI uploads those manifest and lock files to SonarQube for analysis and sends the resolved dependency snapshot derived from them; your source code stays on your machine.”
-
No issue locations Report an error
“SonarQube CLI does not report issue locations for dependency risks. Each finding identifies the package and version that carries the risk, not the line where the dependency is declared.”
-
Default statuses Report an error
“By default, sonar analyze dependency-risks shows active risks (NEW, OPEN, CONFIRM). Override with --statuses.”
-
Status presets Report an error
“Preset Expands to active NEW, OPEN, CONFIRM to_fix NEW, OPEN, CONFIRM, ACCEPT all NEW, OPEN, CONFIRM, ACCEPT, SAFE, FIXED”
-
Severity filter Report an error
“Pass --min-severity to exclude risks below a threshold. Allowed values are BLOCKER, HIGH, MEDIUM, LOW, and INFO (case-insensitive).”
-
Output formats Report an error
“Pass --format to switch between the default table output, structured JSON, and TOON for AI agents.”
-
Risk group types Report an error
“Each groups[] entry groups risks by type (VULNERABILITY, PROHIBITED_LICENSE, or MALWARE).”
-
Recommendation actions Report an error
“the suggested action, such as UPGRADE_PACKAGE, REMOVE_PACKAGE, REVIEW_LICENSE, or NO_FIX_AVAILABLE”
-
Severities statuses Report an error
“Each risk has a severity (BLOCKER, HIGH, MEDIUM, LOW, or INFO) and a status (NEW, OPEN, CONFIRM, ACCEPT, SAFE, or FIXED; NEW is synthesized for newly introduced packages with no server-side status yet).”
-
Toon omissions Report an error
“TOON output mirrors the JSON structure with a few omissions tuned for LLM consumption: partialFixes on vulnerability risks are omitted”
-
Manifest discovery Report an error
“The scanner reads dependency manifests and lock files under the project root across every language and package manager SonarQube SCA supports.”
-
Server settings fetch Report an error
“It fetches the current values from the server on each run, so changes made in the SonarQube UI take effect immediately.”
-
Project not created Report an error
“The project exists on the server. sonar analyze dependency-risks analyzes against an existing project key. It does not create one.”
-
Auto detect project Report an error
“When you omit --project, SonarQube CLI auto-detects that project (see Project key auto-detection) and prints the key to stderr (Using auto-detected project key: …).”
-
Org check cloud Report an error
“On SonarQube Cloud, the CLI also checks that the project belongs to the active organization before it scans.”
-
Stdout payload only Report an error
“The final results always go to stdout, so piping --format json or --format toon into another tool will not mix progress text into the payload.”
-
Nested projects unsupported Report an error
“Nested project directories are not supported yet.”
-
Hook monorepo Report an error
“In a monorepo linked with .sonar-config.json, the hook scans each linked project that contains a changed manifest, from that project's root.”
-
Hook failure behavior Report an error
“A scanner or network failure on one project skips that project.”
-
AI agents Report an error
“An AI coding agent can call sonar analyze dependency-risks like any other shell command, read the structured output, and propose a version bump that clears the vulnerabilities.”
-
Cloud check failure Report an error
“A different organization exits with code 1 and names that organization. Run sonar auth org <organization> to switch.”
-
License risk fields Report an error
“License risks add spdxLicenseId and releaseLicenseExpression (either may be null).”
Scores citing this record
- The Application Security Engineer Dependencies (SCA), licences & secrets
- The Application Security Engineer Developer workflow, quality gates & fixes
- The Engineering Manager Dependencies (SCA), licences & secrets
- The Engineering Manager Developer workflow, quality gates & fixes
- The Lead Developer Dependencies (SCA), licences & secrets
- The Lead Developer Developer workflow, quality gates & fixes
- The Platform Engineer Dependencies (SCA), licences & secrets
- The Product Security Officer Dependencies (SCA), licences & secrets
- The Product Security Officer Developer workflow, quality gates & fixes
- The Skeptic Dependencies (SCA), licences & secrets
- The Skeptic Developer workflow, quality gates & fixes