Sonatype Lifecycle
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Sonatype, Inc. · www.sonatype.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Sonatype Lifecycle at a glance
- Vendor
- Sonatype, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Outside the EU by default source, captured 17 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 17 Nov 2026
- Panel verdict
- The AI panel rates Sonatype Lifecycle 3/5, the mean of 6 judges. Sonatype Lifecycle is a software composition analysis product at its strongest in integration and administration, which scores a flat 7: an OpenAPI 3.0 REST API covering organizations, policies, waivers, audit logs and data retention, SAML 2.0 and OIDC single sign-on, Jira integration, and cloud, on-premises and air-gapped deployment. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Sonatype Lifecycle is a software composition analysis product at its strongest in integration and administration, which scores a flat 7: an OpenAPI 3.0 REST API covering organizations, policies, waivers, audit logs and data retention, SAML 2.0 and OIDC single sign-on, Jira integration, and cloud, on-premises and air-gapped deployment. Dependencies and secrets scores 6-7 on transitive dependency graphs, CycloneDX and SPDX SBOM export, licence reports with legal metadata, malicious-component quarantine and reachability analysis for Java/JVM and JavaScript. Code analysis is weakest, a flat 4: the deep-analysis evidence is a 2021 press release for Sonatype Lift claiming 26+ tools across 11 languages, with no public information on rule sets, OWASP or CWE mapping, or false-positive handling. The bench genuinely splits on sovereignty, which spans 3 to 8: higher scores credit the documented on-premises and air-gapped path that keeps code and findings on the customer's own servers; lower scores weigh Sonatype, Inc. of Fulton, Maryland as data controller and the privacy policy's statement that information may be collected, processed and stored in the U.S. and other countries. Pricing transparency scores 1-2.
Speaks for it
- A broad REST API documented in OpenAPI 3.0 covers organizations, policy evaluation, waivers, audit logs, data retention and roles
- Cloud, on-premises and air-gapped deployment is documented, with a FIPS 140-3 mode for on-premises Lifecycle
- Reachability analysis for Java/JVM and JavaScript, defaulting to off, returns call-path evidence to vulnerable methods
- Pull-request comments on GitHub, GitLab, Bitbucket Server and Azure DevOps fire only for newly introduced violations against the common ancestor commit
- SBOM export covers CycloneDX versions 1.2 through 1.7 (default 1.7) and SPDX 2.2 and 2.3, with licence legal reports and overrides
Held against it
- Deep code analysis is evidenced only by a 2021 press release for Sonatype Lift, a platform the current product pages do not list among Lifecycle, SBOM Manager, Firewall and Repository
- We found no public information on secret detection — detectors, git-history scanning or push protection
- We found no public information on customer source-code retention, whether code trains AI models, or a published SLA or status page
- We found no public information on SCIM provisioning or webhooks for findings, which an enterprise rollout will want
- FIPS 140-3 mode applies only to new on-premises Lifecycle installations, requires a special licence and cannot be converted back to standard mode
Best for
- You run Java/JVM or JavaScript estates and want call-path evidence showing whether vulnerable methods are actually reached
- You must keep code and findings on your own servers, including fully air-gapped networks
- You administer many repositories and want rollout through an organization-hierarchy API with SAML 2.0 single sign-on and Jira notifications
- You gate merges on newly introduced violations only, with a develop stage that fails nothing by default
Avoid if
- You are buying deep static analysis of first-party code and need a published rule set mapped to OWASP and CWE
- You need secret detection, and we found no public information on detectors, git-history scanning or push protection
- You must give an auditor a documented source-code retention or AI-training statement before signature
- You need cloud deployment with EU storage — no page promises EU storage for EU customers, and the privacy policy states storage in the U.S. and other countries
The scores
| Criterion | Panel median |
|---|---|
| Code analysis (SAST & code quality) | 2 of 5 |
| Dependencies (SCA), licences & secrets | 3.5 of 5 |
| Developer workflow, quality gates & fixes | 3 of 5 |
| Platforms, deployment & administration | 3.5 of 5 |
| Source-code handling, security & compliance | 3 of 5 |
| European sovereignty | 3.5 of 5 |
Code analysis (SAST & code quality)
Show reasoningHide reasoning
How this is scored
What the tool finds in the company's own code: static application security testing with data-flow and taint analysis across functions and files, the languages and frameworks covered and at what depth, the rule sets (OWASP Top 10, CWE, custom rules), bugs and code smells, duplication, cyclomatic and cognitive complexity, maintainability and technical-debt measures, test coverage import, infrastructure-as-code checks, and how false positives are measured and kept down.
0 — Does not analyse source code; a dependency, secret or runtime scanner only, or a different kind of product.
3 — Pattern-based rules or linters for a handful of languages; data-flow analysis, the rule list, quality metrics and false-positive handling are basic or not described.
5 — SAST for the common languages (Java, JavaScript/TypeScript, Python, C#, Go, PHP) with the rule list published and mapped to OWASP and CWE, bugs and code smells, duplication and complexity metrics, coverage import, and custom rules or rule configuration documented.
8 — Cross-file taint analysis with the supported frameworks listed per language, a rule language customers can write in, infrastructure-as-code checks, maintainability or code-health scores over time, false-positive rates or benchmarks published, and each finding explained with its data flow and a fix.
10 — Analysis a large polyglot codebase relies on: deep interprocedural analysis across many languages with the depth stated per language, independent benchmark results, quality and security trends per team and hotspot, and every rule documented with examples and its precision.
The Lead Developer
The deep code analysis story rests on a 2021 press release for Sonatype Lift claiming "26+ tools across 11 languages", analysis that catches "bugs that traverse files", and the Infer and ErrorPrune engines — real static analysis, but the specific languages, a published rule set mapped to OWASP and CWE, quality metrics, custom rules and false-positive handling are things we found no public information on in these captures. For a Laravel and TypeScript shop I cannot confirm PHP or framework coverage from these pages. 4 1
The Application Security Engineer
The vendor describes a deep code analysis platform built on Facebook's Infer and Google's ErrorPrune, 26+ tools across 11 languages, with cross-file analysis that catches bugs traversing files — though these claims come from a 2021 launch announcement for a product the current platform pages do not list among Lifecycle, SBOM Manager, Firewall and Repository. We found no public information naming the languages, publishing a rule list mapped to OWASP or CWE, describing custom rules for in-house frameworks, quality metrics, or false-positive handling, so I cannot judge the taint-style analysis my payments teams would rely on. 1 4
The Engineering Manager
The Lift launch material claims deep, cross-file analysis from 26+ tools across 11 languages, built on Facebook's Infer and Google's ErrorProne, catching everything from style issues to complex coding errors in first-party code — a genuine static-analysis claim that interests my Java teams. Beyond that I found no public information on the rule list, OWASP or CWE mapping, complexity or technical-debt metrics, coverage import, custom rules, or false-positive handling, so the depth per language cannot be judged. Nothing here evidences code-health trends per team or hotspot, which is what I would actually buy for. 1 4
The Platform Engineer
The static-analysis evidence is the 2021 Lift launch material: 26+ analysis tools across 11 languages built on Facebook's Infer and Google's ErrorProne, catching bugs that traverse files, from style issues to complex errors in first-party source and third-party libraries. Beyond that I found no public information on a published rule list, OWASP or CWE mapping, quality metrics like duplication and complexity, custom rules, or false-positive handling, and Lifecycle's own analysis story on these pages is dependency-centric. A credible cross-file bug-finding claim, but nothing my teams could audit the rules against. 1 4
The Product Security Officer
The press release documents deep analysis beyond per-file — bugs that traverse files — using 26+ tools across 11 languages built on Facebook's Infer and Google's ErrorProne, which is genuine interprocedural work. That evidence dates from 2021 and concerns the Lift platform, and we found no public information on a published rule list, OWASP or CWE mapping, complexity and maintainability metrics, coverage import, or false-positive handling. For my audit file this demonstrates depth but is thin on rule-set documentation a reviewer would ask for. 1 4
The Skeptic
The deep-analysis evidence is a 2021 launch press release for a platform named Sonatype Lift — 26+ tools across 11 languages and analysis that crosses files — while the engineering documentation captured for Lifecycle concerns components and policies. We found no public information on the rule sets, OWASP or CWE mapping for code findings, quality metrics, or how false positives are measured. Reachability analysis is documented, but for calls into vulnerable dependencies, not first-party code. 4 1 8
Dependencies (SCA), licences & secrets
Show reasoningHide reasoning
How this is scored
What comes from outside or should never be committed: software composition analysis of direct and transitive dependencies with the ecosystems and lockfiles supported, the vulnerability database and how quickly it is updated, reachability analysis, licence detection and policies, SBOM export (CycloneDX, SPDX), malicious and typosquatted package detection, end-of-life components, automatic upgrade pull requests, container image scanning, and secret detection in code and git history with the number of detectors, validity checks and revocation guidance.
0 — No dependency or secret scanning of any kind.
3 — Known-vulnerability alerts for dependencies in one or two ecosystems or a basic secret pattern check; transitive dependencies, licences, SBOMs and git history are basic or not described.
5 — SCA for the main ecosystems including transitive dependencies, licence detection with policies, SBOM export in a standard format, upgrade suggestions or pull requests, and secret detection in commits with the detector list described.
8 — Reachability analysis that shows whether vulnerable code is called, malicious-package detection, the vulnerability database and its sources documented, end-of-life components flagged, secrets checked for validity and scanned across the full git history, and push protection that stops a secret before it lands.
10 — Supply-chain coverage a regulated software maker can file: every ecosystem the company builds with, reachability for each, SBOM and VEX output for customers, licence obligations explained per licence, secrets found outside git (tickets, chat, containers) with automated revocation, and the database's coverage and latency evidenced.
The Lead Developer
Dependency analysis is the well-documented core: direct and transitive dependency graphs, licence data with overrides and legal metadata reports, SBOM export in CycloneDX and SPDX, remediation suggestions that prefer fixes covering the whole dependency tree, reachability analysis for Java and JavaScript showing call paths to vulnerable methods, and extensive malicious-component detection. We found no public information on secret detection, container image scanning or end-of-life flagging in the captured pages. 5 8 9 6 1
The Application Security Engineer
Strong supply-chain side: transitive dependency graphs in CycloneDX 1.4+ scans, malicious-component detection with quarantine and a malware risk dashboard, licence policies with overrides and legal metadata reports, SBOM intake and export in CycloneDX and SPDX, and — most valuable to me — reachability analysis for Java/JVM and JavaScript (default off) that determines the method signatures triggering a vulnerability, plus an API returning call paths to vulnerable methods. We found no public information on secret detection of any kind, end-of-life component flagging, or container image scanning, which leaves the secrets half of my requirement entirely unaddressed on these pages. 1 5 6 8 9
The Engineering Manager
Supply-chain coverage is well evidenced: direct and transitive dependency graphs, reachability analysis for Java/JVM and JavaScript with call-path evidence exposed through an API, malicious-component detection with quarantine, licence metadata and override policies, SBOM export in CycloneDX and SPDX across many versions, and remediation guidance with breaking-change information. I found no public information on secret detection — no detectors, git-history scanning or push protection appear anywhere in the captures — and end-of-life component flagging is also not described. Strong SCA and licensing, but the secrets half of this criterion is dark. 1 4 5 6 8 9
The Platform Engineer
This is the product's core: composition analysis with direct and transitive dependency graphs, reachability analysis for Java/JVM and JavaScript with call-path evidence exposed by API, malicious-component detection with quarantine and namespace-confusion prevention, licence policies with overrides and legal metadata reports, and SBOM export and ingestion in both CycloneDX (1.2 through 1.7) and SPDX (2.2, 2.3), with their own OSS Index as the documented vulnerability source. Remediation suggests a version that fixes the violation plus its dependencies and states the upgrade effort as breaking-change information. I found no public information on secret detection in code or git history, end-of-life component flagging, or how quickly the vulnerability data updates. 4 5 6 8 9
The Product Security Officer
This is the core of what I need per release: SBOM export in CycloneDX (versions 1.2 through 1.7, default 1.7) and SPDX (2.2, 2.3), direct and transitive dependency graphs, licence legal reports with overrides, and quarantine of malicious components with namespace-confusion prevention. Reachability analysis exists for Java/JVM and JavaScript with call-path evidence via API, defaulting to off, and remediation guidance includes the effort a version upgrade takes. We found no public information on secret detection, VEX output, or end-of-life flagging, so I stop short of the top band. 5 6 8 9
The Skeptic
Real documentation here: transitive dependency graphs, CycloneDX and SPDX export across many spec versions, licence data with overrides and legal reports, malicious-component quarantine through Firewall, and reachability analysis for Java/JVM and JavaScript showing whether vulnerable methods are actually called. The data source is named — OSS Index and Sonatype Data Services — but we found no public information on update cadence, end-of-life flagging or container image scanning. We found no public information on secret detection: detectors, git-history scanning or push protection. 5 6 8 9 4
Developer workflow, quality gates & fixes
Show reasoningHide reasoning
How this is scored
Whether developers see and act on the findings where they work: pull and merge request comments and status checks, quality gates that block a merge on new issues, a focus on new code against a baseline, IDE plugins with the same rules as the server, CLI and CI integrations (GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines), pre-commit hooks, triage, suppression and ignore rules with reasons, deduplication, fix suggestions and AI autofix with the model behind it, and scan times.
0 — Findings only in a separate report; no pull request, IDE or CI integration.
3 — A CI step or a dashboard of findings; pull request comments, gates, IDE plugins and triage are basic or not described.
5 — Pull or merge request comments and status checks on the common platforms, a configurable quality gate that can fail a build, a new-code baseline, IDE plugins for the common editors, CI integrations documented, and findings that can be ignored or marked as false positives.
8 — IDE results that match the server rules, gates per branch or project with thresholds per severity, pre-commit or push-time checks, deduplicated findings across tools, fix suggestions or AI autofix as a reviewable change with the model provider stated, and typical scan times documented.
10 — A workflow that keeps noise low on a large team: findings routed to the owning team, every suppression audited with a reason and expiry, autofix with its acceptance rates published, and the gate's behaviour on every supported platform documented with its limits.
The Lead Developer
The merge-request workflow is documented in real depth: summary and line comments on GitHub, GitLab, Bitbucket Server and Azure DevOps, comments tied to new violations against a common-ancestor baseline, suggested remediating versions, auto and manual waivers, and status checks that fail only on a policy's fail action — exactly where my teams want findings. IDE integrations appear only in passing (user tokens required) with nothing on rule parity between editor and server, line comments cover only direct dependencies in Maven, Gradle, NPM and Go, and we found no public information on pre-commit hooks, deduplication, scan times or the model behind automated fixes. 7 8 9 10 5
The Application Security Engineer
Pull request commenting on GitHub, GitLab, Bitbucket Server and Azure DevOps is documented in real depth: comments fire only for violations the change introduces, compared against the common ancestor commit, with line comments carrying remediating versions and a section for pre-existing violations the PR fixes; policy fail actions and CLI exit codes gate builds and branch protection, and waivers cover triage. Jenkins, Bamboo and GitHub Actions integrations are documented. We found no public information on IDE parity with server rules, deduplication, pre-commit or push-time checks, typical scan times, or the model behind the automated dependency fixes. 5 7 8 9
The Engineering Manager
The pull-request workflow is real: comments on GitHub, GitLab, Bitbucket Server and Azure DevOps for newly introduced violations measured against the common ancestor commit, line comments for direct dependencies in Maven, Gradle, NPM and Go, status checks that fail branch protection only on a 'fail' policy action, separate develop and build stages, Jenkins and Bamboo plugins, GitHub Actions with SARIF upload to code scanning, and policy waivers for triage. IDE plugins are mentioned only in passing, and I found no public information on autofix with a stated model provider, pre-commit checks, deduplication or documented scan times. The new-code gate behaviour is exactly what I ask every team to keep, so this sits above mid-range. 3 5 7 8 9 10
The Platform Engineer
Pull request commenting is documented in depth on GitHub, GitLab, Bitbucket Server and Azure DevOps: line comments on direct dependencies in Maven, Gradle, NPM and Go, a new-violation focus against the common ancestor or default-branch report, a section for fixed violations, and remediation versions inside the comment. Gates run through policy fail actions feeding status checks and branch protection, the CLI's exit codes let a Jenkins build fail, and waivers and overrides are managed by API. The pages mention IDE integrations only in passing for token access, and I found no public information on editor coverage matching server rules, pre-commit hooks, deduplication, typical scan times, or the model behind the automated fixes. 5 7 8 9 10
The Product Security Officer
Pull-request commenting is documented in real depth across GitHub, GitLab, Bitbucket Server and Azure DevOps: three comparison bases for the new-code focus, per-branch develop and build stage recommendations, status checks that fail branch protection on a fail action, line comments with remediating versions for Maven, Gradle, NPM and Go, and both automatic and manual policy waivers. CI integration is concrete — GitHub Actions on the Marketplace with SARIF output and exit codes for pipeline gating, plus Jenkins and Bamboo plugins. We found no public information on IDE plugin behaviour, scan times, or which model powers the automated dependency fixes. 7 8 9 10
The Skeptic
Pull-request comments on GitHub, GitLab, Bitbucket Server and Azure DevOps, line comments on direct dependencies, evaluation against the common ancestor commit so only new violations surface, a develop stage that fails nothing by default while branch protection can fail a build, and Jenkins, Bamboo and GitHub Actions documented with exit codes. Automatic and manual policy waivers give real triage. We found no public information on IDE parity with server rules, scan times, deduplication, or which model powers the promised automated dependency fixes. 7 8 5 9
Platforms, deployment & administration
Show reasoningHide reasoning
How this is scored
How the tool fits the company: the code hosts supported (GitHub, GitLab, Bitbucket, Azure DevOps) cloud and self-managed, a self-hosted or on-premise edition or a scanner that runs inside the customer's network, a documented REST API and webhooks, issue tracker integrations (Jira), single sign-on (SAML or OIDC) and SCIM, roles and permissions per project and team, portfolio reports across repositories, audit logs, export of findings (SARIF, CSV), and partner or multi-organisation accounts.
0 — One repository at a time with no integrations and no administration.
3 — A web dashboard and one code host; the API, roles, SSO and self-hosted options are basic or not described.
5 — GitHub, GitLab and Bitbucket or Azure DevOps supported, a documented REST API, Jira integration, roles per organisation and project, single sign-on, reports across repositories, and export of findings in a standard format.
8 — Self-managed code hosts supported, a self-hosted edition or an in-network scanner documented, SCIM provisioning, audit logs, granular roles per team, portfolio dashboards with trends, SARIF import and export, and webhooks for findings.
10 — Administration that scales across many teams and business units: every setting reachable by API with parity stated, an air-gapped deployment documented, SSO enforced with SCIM, audit logs exportable to a SIEM, and multi-organisation or partner management.
The Lead Developer
Administration is broad and well documented: cloud, on-premises and air-gapped deployment, a Swagger/OpenAPI 3.0 REST API covering organisations, policies, waivers, audit logs and system configuration, SAML 2.0 and OIDC single sign-on, Jira integration for Cloud/Server/Data Center, and role-based access with an organisation hierarchy. We found no public information on SCIM provisioning, webhooks for findings or portfolio trend dashboards on the captured pages. 3 9 10 7 12
The Application Security Engineer
A versioned REST API in OpenAPI 3.0 covers organisations, policy evaluations, waivers, audit logs, data retention and system configuration; SAML 2.0 and OIDC single sign-on, role-based access control, Jira notifications, self-managed code hosts, and SARIF and CSV export are all documented. On-premises, air-gapped and FIPS-mode deployments are documented, the FIPS mode only for new on-premises installations. We found no public information on SCIM provisioning, webhooks for findings, or portfolio trend dashboards. 3 7 9 10 12
The Engineering Manager
Administration runs deep: a versioned REST API documented in OpenAPI 3.0 covering organizations, applications, policies, waivers, audit logs, data retention and CI configuration; Jira notifications for policy violations across Jira Cloud, Server and Data Center; SAML 2.0 with detailed attribute bindings plus OIDC; role-based permissions; CSV and SARIF export; and cloud, on-premises and air-gapped deployment including GitHub Enterprise Server support. I found no public information on SCIM provisioning, webhooks for findings, or portfolio trend dashboards across repositories. Jira routing and SSO for my six teams are evidenced; provisioning automation and board-ready trend reporting are not. 3 7 8 9 10
The Platform Engineer
This fits my world: Lifecycle runs on-premises including a FIPS build for new installations and a fully air-gapped option, it evaluates against self-managed GitHub Enterprise Server, GitLab 11+, Bitbucket Server and Azure DevOps Server 2019+, and the REST API in OpenAPI 3.0 is broad enough to roll settings out to hundreds of repositories — CI configuration with organisation-hierarchy inheritance, system properties, feature toggles, roles, waivers, audit logs and report retention. SAML 2.0 single sign-on is thoroughly documented with signature validation and an SSO-only mode, an OIDC configuration API exists, Jira is covered on Cloud, Server and Data Center, and SARIF generation plus CSV export are documented. I found no public information on SCIM provisioning, webhooks for findings, or portfolio trend dashboards — with no SCIM I would have to run LDAP alongside SAML for group authorisation, which the documentation itself recommends. 3 7 8 9 10 12
The Product Security Officer
On-premises and air-gapped deployment are documented, self-managed code hosts are covered (Bitbucket Server, Azure DevOps Server, GitHub Enterprise), and the OAS 3.0 REST API is unusually broad — organisations, roles and role memberships, audit logs, data-retention policies, Jira configuration, SAML, OIDC and Crowd. CSV export via advanced search and SARIF output round out the reporting. We found no public information on SCIM provisioning, webhooks for findings, or SARIF import. 3 7 9 10
The Skeptic
An unusually broad REST API documented to OAS 3.0 — organizations hierarchy, policy evaluation, waivers, licence and security overrides, audit logs, data retention, roles, SMTP and proxy configuration — plus Jira, SAML 2.0 and OIDC single sign-on, and self-managed hosts such as GitHub Enterprise Server, Bitbucket Server and Azure DevOps Server. On-premises and air-gapped editions are documented, and findings export to SARIF and CSV. We found no public information on SCIM provisioning or webhooks for findings, which an enterprise rollout will want. 9 7 10 3 8 12
Source-code handling, security & compliance
Show reasoningHide reasoning
How this is scored
What the vendor does with the customer's source code and how it holds up in an audit: whether code leaves the customer's network or only results do, where and how long code and findings are stored, whether code or findings are used to train AI models and how to opt out, encryption, the vendor's own certifications (ISO 27001, SOC 2) with their scope, a stated availability or SLA and a public status page, audit logs, and reports mapped to OWASP, CWE, PCI DSS, ISO 27001 or the EU Cyber Resilience Act.
0 — Nothing on how source code is handled, secured or retained.
3 — A security page with general claims; code retention, AI training, certifications and the status page are basic or not described.
5 — How source code is accessed and whether it is stored is described, encryption in transit and at rest, SOC 2 or ISO 27001 stated, a public status page, a statement on whether code trains AI models, and compliance reports mapped to OWASP or CWE.
8 — Code retention periods stated, an option where code never leaves the customer's network, AI features documented with their model provider and an opt-out, certifications with scope and reports available on request, an SLA published, and reports mapped to several standards including PCI DSS or the Cyber Resilience Act.
10 — Source-code handling evidenced end to end: a data-flow diagram of what is sent where, zero retention options, independent audits published with scope, AI processing that can run on the customer's own models, and compliance evidence an auditor can export without asking the vendor.
The Lead Developer
There is a self-service Trust Center with SOC 2 Type II reports and annual penetration-test attestations, encryption with TLS 1.2+ and AES-256, and a documented FIPS 140-3 mode for on-premises installations — useful for regulated clients. But the captured pages say nothing about how long source code or scan findings are retained or whether code trains AI models, and the privacy policy covers only personal-data retention, states storage "in the U.S. and other countries", and explicitly says security cannot be guaranteed. 11 2 12 3
The Application Security Engineer
For the audit file: a self-service Trust Center with SOC 2 Type II reports and annual third-party penetration test attestations, TLS 1.2+ and AES-256, a FIPS 140-3 mode for on-premises deployments, and an on-premises or air-gapped option that keeps analysis inside our network. What I still cannot hand an auditor from these pages: a stated retention period for source code, a statement on whether code trains AI models and how to opt out, a published availability SLA or status page, and findings mapped to PCI DSS or the Cyber Resilience Act — the OWASP reference describes the vendor's own development lifecycle, not customer-facing compliance reports. 2 3 11 12
The Engineering Manager
The vendor's own security posture is well evidenced: SOC 2 Type II reports and penetration-test attestations via a self-service Trust Center, TLS 1.2+ and AES-256, MFA and least-privilege controls, annual continuity testing, and an unusually detailed FIPS 140-3 mode for on-premises Lifecycle. I found no public information on how customer source code is stored or retained, whether code trains AI models, a status page, an SLA, or findings mapped to OWASP, CWE or PCI DSS. I would arrive at an audit with their certificates but no source-handling story. 2 3 11 12
The Platform Engineer
The vendor's own security posture is well evidenced: SOC 2 Type II reports and annual third-party penetration-test attestations through a self-service Trust Center, TLS 1.2+ and AES-256, a security program aligned to ISO 27001 and NIST, and a documented FIPS mode for on-premises Lifecycle with AES-GCM and FIPS-certified cryptography. What I could not find on the captured pages is anything on how customer source code is handled or retained, whether code trains AI models, a public status page or service level agreement, or product findings mapped to OWASP, CWE or PCI DSS — the OWASP reference covers their own development process. Report purging is configurable by API, which at least gives me retention control over findings on my own server. 2 9 11 12
The Product Security Officer
For my audit file there is real substance: a self-service Trust Center with SOC 2 Type II reports and annual penetration-test attestations, a secure SDLC aligned with OWASP, and a FIPS 140-3 page precise to the algorithm and keystore level for on-premises Lifecycle. The published retention figures, however, cover personal data such as six years for account records, not customer source code; and we found no public information on a status page, an availability SLA, or any statement on whether code or findings are used to train AI models. Reports mapped to standards such as PCI DSS or the Cyber Resilience Act are also not in evidence. 2 11 12
The Skeptic
SOC 2 Type II reports sit behind a self-service Trust Center, annual third-party penetration tests of core products are attested, encryption is stated as TLS 1.2+ and AES-256, and a FIPS 140-3 mode exists for on-premises Lifecycle — new installations only, special licence, and irreversible. The privacy policy covers personal-data retention and names Sonatype Inc. as controller, but we found no public information on source-code retention, whether code trains AI models, a published SLA or status page, or customer reports mapped to OWASP, CWE, PCI DSS or the Cyber Resilience Act. 11 2 12 9
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where source code, findings, SBOMs, account and usage data are stored and processed, and who the subprocessors are (hosting, AI models used for autofix and triage, vulnerability data sources, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Public vulnerability databases and package registries the scanner queries are part of what the product does and are not counted against it; where the customer's code and findings are stored and who processes them is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (AI models, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps code and findings on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Lead Developer
The contracting entity and data controller is Sonatype, Inc. of Fulton, Maryland, storage is stated as "the U.S. and other countries" with production on AWS, the captured pages list no subprocessors beyond subsidiaries and recipients of aggregated data, and we found no data processing agreement on these pages. The documented on-premises and air-gapped options, including Lifecycle FIPS installations on customer servers, would let a European customer keep code and findings in their own environment, which keeps this above the floor. 2 11 3 12
The Application Security Engineer
The contracting entity is Sonatype, Inc. of Fulton, Maryland, production runs on AWS, and the privacy policy says data may be collected, processed and stored in the U.S. and other countries; we found no public information promising EU storage, naming the subprocessors, or offering a data processing agreement. Decisive for us: a documented on-premises edition — FIPS mode exists only for new on-premises installations — together with a documented air-gapped deployment, so Lifecycle can run on our own European servers with code and findings staying in our chain. 2 3 11 12
The Engineering Manager
The contracting entity is Sonatype, Inc. of Fulton, Maryland, and the privacy policy states information may be collected, processed and stored in the U.S. and other countries; subprocessors are not listed and I found no captured data processing agreement or page promising EU storage for EU customers. What lifts this is the documented on-premises and air-gapped deployment, confirmed for Lifecycle by the on-premises FIPS documentation, which would keep code and findings in our own European chain — though data updates in air-gapped environments are noted to take longer. For the cloud edition I see no European route. 2 3 12
The Platform Engineer
For my deployment model the decisive facts are that Lifecycle is documented running on-premises, with a FIPS build for new installations and a deployment option described as fully air-gapped that avoids the public internet — code and findings stay on my servers, and the vulnerability data feed is public package data. The vendor itself is Sonatype, Inc. of Fulton, Maryland, a US data controller that states information may be stored in the US and other countries and relies on the EU-US Data Privacy Framework for transfers. I found no published data processing agreement and no list of subprocessors with their locations on the captured pages. 2 3 11 12
The Product Security Officer
The customer chain can stay in-house: Lifecycle runs as on-premises installations — the FIPS documentation is written for them — and cloud, on-premises and air-gapped models are documented with full control of environment, infrastructure and assets, so code and findings can remain on my own servers. The vendor chain is squarely American: Sonatype, Inc. of Fulton, Maryland is the controller, information may be collected and stored in the U.S. and other countries, and production runs on AWS. We found no public information on an EU contracting entity or representative, a published data processing agreement, or a subprocessor list, and the deployment page capture leaves open which products run under which model. 2 3 11 12
The Skeptic
The contracting entity is Sonatype, Inc. of Fulton, Maryland; the privacy policy says data may be processed and stored in the U.S. and other countries, production runs on AWS, and we found no public information on EU hosting, a published data processing agreement, or a subprocessor list. The documented on-premises and air-gapped path — Lifecycle's FIPS page confirms on-premises installations — lets a European customer keep code and findings on its own servers, though the captured deployments page does not show which products are available under each model. 2 11 3 12
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per developer, contributor, committer or line of code and per plan, how contributors are counted, what the free tier and open-source plan include, which scanners (SAST, SCA, secrets, containers) and features (SSO, self-hosting, AI autofix, compliance reports) cost extra, limits on repositories, scans or lines of code, minimum seats, monthly versus annual terms, and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price exists, but how developers or lines of code are counted and what the add-ons cost is unclear.
5 — Plans are public with their price per developer or per lines of code and main inclusions, but at least one commonly needed piece (SSO, self-hosting, an extra scanner, AI autofix or the enterprise tier) is unpriced or "contact sales".
8 — Every plan priced publicly with its counting rule (active contributors, lines of code) explained, scanners and add-ons priced, limits on repositories and scans stated, a free or open-source tier with its limits, and monthly and annual terms and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of developers, repositories and lines of code, with every scanner, add-on, self-hosted licence and support level priced and the cancellation and data-export terms published.
The Lead Developer
The captured pricing page shows no prices at all; the only concrete pricing facts are that Lift is "free forever for public repositories", that technical support is included in the subscription at no additional cost, and that Repository Firewall needs a separate licence on Nexus Repository Pro. How developers or contributors are counted, plan prices, seat minimums, monthly versus annual terms and VAT treatment are things we found no public information on — for a fourteen-developer agency with freelancers I cannot compute an annual cost from these pages. 3 4 6 1
The Application Security Engineer
The only price statement we found is that Lift will be free forever for public repositories, from a 2021 press release, and the deployments page shows a Pricing heading with no figures. We found no public information on plan prices, how developers or lines of code are counted, free-tier limits, or the cost of add-ons such as the additional Repository Firewall license required for Nexus Repository Pro users. 3 4
The Engineering Manager
The captured pricing page states no prices, and the only public price statement I found is that Lift will be free forever for public repositories — which does nothing for my private repositories. Per-developer pricing, counting rules, plan inclusions, add-on costs, repository or scan limits, seat minimums, monthly versus annual terms and VAT treatment are all absent from the pages read. For a commercial deployment, everything is a sales conversation. 1 3 4
The Platform Engineer
The captured pricing page states no prices, and no per-developer or per-repository figures, counting rules, seat minimums or VAT terms appear in the captured material. The only price-relevant statements are that Lift will be "free forever for public repositories", that support is included in the subscription for all three deployment options, that Repository Firewall needs an additional license on Nexus Repository Pro but not Pro+, and that FIPS mode requires a special Lifecycle license — none of them priced. I cannot compute an annual cost for 300 developers and 900 repositories from these pages. 3 4 6 12
The Product Security Officer
The captured deployments page carries a pricing section that states no prices, and we found no public information on per-developer or per-line rates, plan contents, seat counting, or what SSO, self-hosting or the individual modules cost. The only pricing statements anywhere are that Lift is free forever for public repositories and that products are available through AWS Marketplace. For a regulated buyer the annual cost is not computable from these pages. 3 4
The Skeptic
The captured pages state no prices at all, and we found no public information on per-developer or per-contributor rates, how anyone is counted, seat minimums, term lengths or VAT. The only pricing statement found is a 2021 press release promising 'Lift will be free forever for public repositories'. Firewall capability needs an additional licence for Repository Pro users and is bundled only into Pro+, so even the packaging is invisible without a sales conversation. 3 4 6
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?The statement is qualified with "may" and addresses users outside the United States rather than naming a default hosting location; no page promises EU storage for EU customers. |
0/4 pts | 2 Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?The "AVAILABLE FOR" product lists under each deployment model are empty in the excerpt, so which products are self-hostable is not shown. |
1/1 pts | 3 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Sonatype Lifecycle
Is Sonatype Lifecycle European?
Not determined: the vendor’s pages as captured do not say where Sonatype Lifecycle is based.
Where does Sonatype Lifecycle store data?
Sonatype Lifecycle stores customer data outside the EU by default, per the vendor’s page captured 17 Nov 2026.
Does Sonatype Lifecycle have a free plan?
Yes. Sonatype Lifecycle has a free plan, per the vendor’s page captured 17 Nov 2026.
What are the best alternatives to Sonatype Lifecycle?
As of 19 Nov 2026, the panel rates SonarQube (3.5/5), Aikido Security (3.5/5) and Endor Labs (3.5/5) highest among the other 18 Code Security & Quality (SAST/SCA) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is SonarQube (EU origin, foreign-owned, Switzerland). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Sonatype Lifecycle alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The statement is qualified with "may" and addresses users outside the United States rather than naming a default hosting location; no page promises EU storage for EU customers.
- Weak sourcing — Hosting options. The "AVAILABLE FOR" product lists under each deployment model are empty in the excerpt, so which products are self-hostable is not shown.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.sonatype.com Checked 17 Nov 2026 Details →
- 2 Privacy policy — found from the homepage www.sonatype.com Checked 17 Nov 2026 Details →
- 3 Self-hosting / on-premises installation docs — found from the homepage www.sonatype.com Checked 17 Nov 2026 Details →
- 4 Code analysis (SAST & code quality) — found from sitemap www.sonatype.com Checked 17 Nov 2026 Details →
- 5 Dependencies (SCA), licences & secrets — found from sitemap help.sonatype.com Checked 17 Nov 2026 Details →
- 6 Dependencies (SCA), licences & secrets — found from sitemap help.sonatype.com Checked 17 Nov 2026 Details →
- 7 Developer workflow, quality gates & fixes — found from sitemap help.sonatype.com Checked 17 Nov 2026 Details →
- 8 Developer workflow, quality gates & fixes — found from sitemap help.sonatype.com Checked 17 Nov 2026 Details →
- 9 Platforms, deployment & administration — found from sitemap help.sonatype.com Checked 17 Nov 2026 Details →
- 10 Platforms, deployment & administration — found from sitemap help.sonatype.com Checked 17 Nov 2026 Details →
- 11 Source-code handling, security & compliance — found from sitemap www.sonatype.com Checked 17 Nov 2026 Details →
- 12 Source-code handling, security & compliance — found from sitemap help.sonatype.com Checked 17 Nov 2026 Details →