Source
Developer workflow, quality gates & fixes — found from sitemap — Sonatype Lifecycle
Checked for Sonatype Lifecycle on 17 Nov 2026
- Page
- https://help.sonatype.com/en/sonatype-github-actions.html
- Checked
- 17 Nov 2026, 12:00 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:1a347c2efac42ea5b0db70bc5979e12ee913314452b8e9b60eef1cd043111b9e
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Github actions overview Report an error
“This integration provides a set of GitHub Actions for interacting with different Sonatype products directly within your GitHub workflows.”
-
Github code scanning support Report an error
“Sonatype GitHub Actions also support integration with GitHub Code Scanning, part of the GitHub Advanced Security feature, which displays detected vulnerabilities on the GitHub Security and quality tab.”
-
Github advanced security availability Report an error
“GitHub Advanced Security is available for GitHub Enterprise customers and public repositories.”
-
Github marketplace Report an error
“The Sonatype GitHub Actions integration is available on the GitHub Marketplace.”
-
Evaluate action Report an error
“An action for evaluations against a Sonatype Lifecycle instance in GitHub workflows. It sets up Sonatype CLI and runs it to execute the evaluation.”
-
Fetch sbom action Report an error
“An action for retrieving an SBOM (Software Bill of Materials) file associated with a previous Lifecycle evaluation. It supports both the CycloneDX and SPDX standards.”
-
Evaluate action sarif output Report an error
“Generates a SARIF file with a specified name containing all identified vulnerabilities. The SARIF file extension must be .sarif or .json.”
-
Upload sarif parameter Report an error
“Enable this parameter to generate or use the generated sarif-file to update the "Code scanning" section under the GitHub repository's Security tab. Default: false.”
-
Reachability analysis java Report an error
“Since version 1.4.0, you can perform a Reachability Analysis in Java or JVM language binaries to determine the method signatures that trigger a security vulnerability. Default: false.”
-
Reachability analysis js Report an error
“Enable Reachability Analysis for JavaScript projects. Default: false.”
-
Sbom versions Report an error
“Available CycloneDX versions: 1.2, 1.3, 1.4, 1.5, 1.6, 1.7. Default version for CycloneDX is 1.7. Available SPDX versions: 2.2, 2.3”
-
Dependency graph push Report an error
“If set, the dependency information from the fetched SBOM will be available in GitHub Insights Dependency Graph. Default: false.”
-
Evaluate action outputs Report an error
“scan-id Scan id result of the run operation. It can be used to access the Lifecycle report of related artifacts. report-url Link to navigate directly to the analysis report in Lifecycle (IQ Server).”
-
Exit codes Report an error
“0 Success 1 Policy violation 2 Scanning error 3 Reachability error 4 Configuration error 5 Connectivity error 6 Local I/O error 7 Authentication error”
-
Cli output variables Report an error
“The pipelines now emit the following output variables: Output Variable Description Values cli-exit-code”
-
Ci configuration API Report an error
“To centrally manage supported CI evaluation settings for GitHub Actions workflows through the Lifecycle organization and application hierarchy, see the CI Configuration REST API.”
-
Sha256 checksums Report an error
“If set, SHA256 checksums are included in the scan file. Default: false.”
-
Default lifecycle stage Report an error
“Specify the development lifecycle stage for the analysis. Defaults to the build stage.”
-
Ghes artifact limitation Report an error
“it's because GHES doesn't currently support @actions/upload-artifact@v4. To resolve this, add the following step to your workflow to use @actions/upload-artifact@v3 instead:”
-
Security events permission Report an error
“In order to use the GitHub Advanced Security feature, you must grant your workflow the security-events: write permission.”
-
Automatic application creation Report an error
“When Automatic Applications is enabled and the application ID has not yet been used, a new application will be created with the given ID.”
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 Engineering Manager Platforms, deployment & administration
- The Lead Developer Dependencies (SCA), licences & secrets
- The Lead Developer Developer workflow, quality gates & fixes
- The Platform Engineer Dependencies (SCA), licences & secrets
- The Platform Engineer Developer workflow, quality gates & fixes
- The Platform Engineer Platforms, deployment & administration
- The Product Security Officer Dependencies (SCA), licences & secrets
- The Product Security Officer Developer workflow, quality gates & fixes
- The Skeptic Code analysis (SAST & code quality)
- The Skeptic Dependencies (SCA), licences & secrets
- The Skeptic Developer workflow, quality gates & fixes
- The Skeptic Platforms, deployment & administration