Generate Software Bill of Materials (SBOM) directly from your Delphi projects
– without additional tools and ready for integration into existing workflows.
An SBOM is a structured list of all the components, libraries and dependencies of an application.
Generate Software Bill of Materials (SBOM) directly from your Delphi projects
– without additional tools and ready for integration into existing workflows.
Whether it's a support request, a suggestion for improvement, or a new feature request—you can easily submit your request through our ticket system and track its status at any time.
Thank you very much! Your ticket has been created.
The generated SBOM is provided as a CycloneDX JSON file.
This format enables: - standardized use in security and compliance tools - sharing with customers, partners, or auditors - integration into existing analysis and monitoring systems The focus is not only on creation, but on direct processing.
In addition to IDE integration, a CLI version is available that can be flexibly integrated into existing processes.
Typical scenarios: - SBOM creation in automated builds - Integration into CI/CD pipelines - Processing of CycloneDX files in downstream systems Can be used both locally in the IDE and fully automated.
The system takes existing SBOMs into account and automatically supplements missing information. This creates a complete and consistent SBOM – even with incomplete source data.
This means: - existing SBOMs are automatically adopted - integration along dependencies (parent-child principle) - automatic generation of virtual SBOMs for components without their own SBOM - centralized management of this information
Unlike generic SBOM tools, this solution is specifically developed for Delphi.
This means: - better detection of Delphi-specific components - direct integration into the development process - less manual effort Additionally, there is a cooperation with Embarcadero to integrate the SBOM function even more deeply into the Delphi ecosystem in the future.
Many existing applications are based on legacy Delphi codebases.
This often leads to: - incomplete documentation of dependencies - lack of automated solutions manual and error-prone processes - no unified library management system - components and dependencies are often distributed across the entire hard drive Generic SBOM tools are often not suitable for this.
The Cyber Resilience Act (CRA) establishes new requirements for the security and transparency of software products.
Companies will need to: - document deployed components - make dependencies traceable - provide SBOMs Automated SBOM generation thus becomes a central component of modern software development.
A Software Bill of Materials (SBOM) is a structured listing of all components, libraries, and dependencies of an application.
It is typically provided in formats such as CycloneDX JSON and serves to:
Sign up here to receive information and updates about our SBOM Generator.
Vielen Dank für Ihre Unterstützung und Ihre Mithilfe zur Verbesserung des Produktes.
Thank you very much for your support and for helping us to improve the product.
Sign up here to receive information and updates about our SBOM Generator.
Disclaimer:
Our new software is currently in the beta phase. You can try it out for free and help us improve it by providing your feedback. Please note that this is a pre-release version which may still contain bugs.
This software is currently in the beta phase. This version is intended solely for testing and evaluation purposes.
The beta version may contain errors, limitations or unexpected behaviour. It is provided ‘as is’, without any express or implied warranty.
No warranty claims apply to the beta version.
You use the software at your own risk.
We accept no liability for any damage, loss of data or consequential loss arising from the use of the beta version.
Features may be modified, expanded or removed at any time. We are under no obligation to continue the beta version or to provide a final version.
By using this software, you agree that anonymised feedback may be used to improve the software – unless you object to this.
The beta version is not intended for use in production business environments or safety-critical scenarios.
