Nexus One Platform

Searches the organization-wide SBOM inventory by component, version or CVE and returns the affected products, projects and environments, so a newly disclosed vulnerability or a suspect package can be traced to everywhere it ships.

Creates, imports, and manages Vulnerability Exploitability eXchange statements asserting the exploitability status of CVEs for specific product versions, reducing false positive noise for downstream consumers.

Generates SBOMs from source code analysis (via build system integration), and from binary analysis (via binary composition analysis), the latter enabling SBOM generation for third-party software where source is unavailable.

Normalizes ingested SBOMs to the CISA minimum elements by resolving missing or inaccurate component identifiers such as PURL and CPE and dependency relationships, and enriches components with license, supplier and support metadata, so SBOMs from any generator can be analyzed for third-party risk consistently.

Generates formatted evidence packages for SBOM-related regulatory requirements: FDA pre-market cybersecurity guidance, Executive Order 14028 SBOM requirements, EU Cyber Resilience Act Article 13.

Tracks the support level and end-of-support date of each SBOM component, flagging components that will lose security maintenance while the product is still on the market. Covers the two per-component elements FDA premarket cybersecurity guidance requires beyond the NTIA baseline.

Tracks license obligations across the SBOM inventory, identifying GPL and AGPL copyleft propagation, license conflicts, and FOSS obligations for each release.

Manages the SBOM life cycle including discovery, access and secure exchange between software suppliers and consumers.

Monitors SBOMs against live vulnerability feeds, alerts when new CVEs affect components in managed SBOMs. Latency to alert after new CVE publication varies.

Imports and exports SBOMs in CycloneDX, SPDX, and SWID formats, enabling interoperability with scan tools, procurement workflows, and regulatory evidence systems.

Determines whether a vulnerable function is actually reachable and invoked, not merely present in the dependency tree, cutting actionable CVEs down to those with real exploit paths. Delivered either statically, by call-graph analysis layered on dependency scanning, or at runtime, by instrumenting the workload to observe which components actually execute.

Opens PRs with upgraded dependency versions that resolve CVEs. Quality differentiation is whether the fix resolves transitive chains or only direct dependencies, and whether the PR is merge-safe without manual review.

Identifies OSS licenses in the dependency tree and flags conflicts with the project's target license or policy (GPL contamination, copyleft obligations, export-controlled components). Separate from vulnerability detection.

Scans images stored in registries (ECR, GCR, Artifact Registry, Docker Hub), for vulnerable OS packages and application dependencies at push time or on schedule, without requiring a running container.

Traverses the full dependency graph to surface CVEs in indirect dependencies, packages required by your direct dependencies. Direct-only scanning misses the majority of vulnerable code paths in modern polyglot projects.

Defines open source policies (banned licenses, blocked packages, version floors, severity gates) as version-controlled rules applied automatically at scan time across repositories.

Blocks or flags PRs in CI/CD pipelines based on policy-defined thresholds, configurable by severity, CVSS score, exploitability, fix availability, or CVE age. Prevents vulnerable code from merging without requiring zero-tolerance policies.

Imports or generates Vulnerability Exploitability eXchange documents asserting whether a known CVE actually affects a given product in its deployed context, including statements derived from reachability analysis so an SBOM ships with evidence-backed exploitability. Reduces false positives in downstream consumers of SBOMs.

Scores open source dependency health using release cadence, maintainer count, contributor reputation, and popularity, flagging abandoned packages beyond known CVEs.

Identifies packages with known-malicious behavior (typosquatting, dependency confusion, backdoored releases), distinct from packages with CVEs in legitimate code.

Exports the dependency inventory as a machine-readable Software Bill of Materials in SPDX or CycloneDX format, consumable by downstream vulnerability scanners, compliance tools, and procurement workflows.

Governs third-party software consumption to apply consistent software supply chain security policy.

Detection and provenance tracking of AI and ML components, models, and LLM usage within the software supply chain.

Risk context for open-source dependencies including reachability, exploitability, and upgrade impact.

Compiles vendor, third-party and open-source maintainer reputation to flag risk from unmaintained, deprecated or abandoned software.

Deep analysis of binaries and packages to detect tampering, malware, and hidden threats beyond manifest-based scanning.

Live visibility into code, components, pipelines, and developer activity across the software development lifecycle.