New release adds a full command-line interface for continuous integration, Software Bill of Materials (SBOM) generation ahead of the EU Cyber Resilience Act, and native NI Package Manager support
[City, State] – DATE, 2026 – JKI announced the release of VIPM 2026 Q3, the latest version of its VI Package Manager for LabVIEW. The release introduces a complete command-line interface (CLI) for continuous integration (CI) automation, a new vipm sbom command for generating Software Bills of Materials ahead of the EU Cyber Resilience Act (CRA), and support for managing NI Package Manager (NIPM) dependencies alongside VIPM packages in a single configuration file. VIPM 2026 Q3 is available for download now.
"How can I run VIPM in CI to install my project's packages in LabVIEW?" has been the most-requested feature among LabVIEW teams for several years, according to JKI. VIPM 2026 Q3 answers that request directly, while also giving teams a compliance-ready path to a requirement set by EU law: documenting the components in any product with digital elements sold into the EU.
VIPM 2026 Q3 ships a complete, standalone command-line interface: not a wrapper around the desktop application, but a full program with its own commands, options, and built-in help. The CLI starts VIPM Desktop and LabVIEW behind the scenes only when a job requires them, and is designed to run unattended on build servers with no screen, mouse, or operator present.
Representative commands include:
vipm install oglib_boolean
vipm install MyProject.vipc --labview-version 2026
The CLI is built in Rust, compiling to a single native executable with no separate runtime to install, and supports Windows, macOS, and Linux from one codebase. JKI already ships Rust-backed LabVIEW libraries for TOML parsing and high-performance HTTP.
A reference GitHub Actions workflow is available in the Getting Started with the CLI guide and the examples repository, and installs a project's dependencies from a .vipc or vipm.toml file inside NI's official LabVIEW 2026 Q3 container image. Equivalent guides are available for GitLab, Jenkins, and Azure DevOps.
The full CLI Command Reference documents every command and option. The CLI includes a set of features designed specifically for unattended operation:
The EU Cyber Resilience Act applies to products with digital elements sold into the EU. Two compliance dates are directly relevant to LabVIEW-based products: mandatory 24-hour reporting of actively exploited vulnerabilities and severe incidents beginning 11 September 2026, and the full application of essential requirements, including the obligation under Annex I Part II(1) to produce a software bill of materials covering top-level dependencies, beginning 11 December 2027.
VIPM 2026 Q3 introduces vipm sbom, a new command that generates a Software Bill of Materials directly from a vipm.toml, .lvproj, .dragon, or .vipc file:
vipm sbom --from MyProject.lvproj
vipm sbom --from vipm.toml
Full details are available in the SBOM guide. The command emits CycloneDX 1.5, one of the two SBOM formats recognized by EU market surveillance authorities. Generated SBOMs cover both VIPM and NI packages, include license identifiers and cryptographic hashes, record the software producer via --product-supplier, and are byte-reproducible: components are emitted in stable, sorted order, with document timestamps that can be pinned via --document-timestamp or SOURCE_DATE_EPOCH. Byte-reproducible output allows an SBOM to be checked into source control and diffed like code, so any change reflects a genuine shift in the supply chain rather than incidental noise.
vipm sbom can also be added directly to a CI pipeline, ensuring the SBOM regenerates, and stays current, on every commit.
LabVIEW 2026 Q3 adds a "Generate SBOM" option directly to build specifications in the LabVIEW Application Builder, producing an SBOM alongside the compiled executable with no CI, containers, or command line required. The generated SBOM is scoped specifically to the VIPM and NI packages used by the VIs included in that build, rather than every package installed on the development machine, aligning with the CRA's Annex I requirement to document only the components actually shipped in the product. The same scoping is available from the command line via:
vipm sbom --from MyProject.lvproj --lvproj-build-spec "My Application"
VIPM 2026 Q3 is available for download today. LabVIEW 2026 Q3, required for the "Generate SBOM" build specification option, is available separately. Full documentation, including the Getting Started with the CLI guide, the SBOM guide, the Docker guide, the GitHub Actions guide, and the NI Packages (NIPM) guide, is available at JKI's documentation site, along with a working examples repository.
For 25 years, JKI has helped engineering teams, in automated test equipment, medical devices, and industrial control, deliver LabVIEW software with confidence. VIPM, JKI's VI Package Manager, is used by LabVIEW teams worldwide to manage, distribute, and automate the delivery of LabVIEW software packages.