Knowledge · Software Supply Chain

SBOM for Delphi Applications

The engineering challenges of dependency discovery in Delphi applications and how SCA-based SBOM generation addresses legacy code, GetIt packages, and non-standard component workflows.

Primary question: How can organizations create and maintain a Software Bill of Materials for Delphi applications?

Definitions

Software Bill of Materials (SBOM)

A formal record containing the details and supply chain links of all components, libraries, and dependencies used to create a software product. An SBOM enables organizations to understand what is in their software and assess vulnerability exposure.

Delphi dependency discovery

The process of identifying all third-party packages, GetIt components, VCL/FMX frameworks, and system libraries used in a Delphi application, which is complicated by Delphi's mixed source/binary distribution model and legacy component ecosystems.

GetIt package manager

Embarcadero's integrated package management system for Delphi and C++Builder, which distributes components, frameworks, and templates. GetIt packages may include pre-compiled binaries and custom installers that complicate automated dependency discovery.

SBOM source resolution

The process of mapping compiled or packaged dependencies back to their original source files and versions, which is particularly challenging for Delphi applications that may use compiled files alongside source distributions.

The engineering problem

Delphi applications often include dependencies that are not declared in standard manifest files, including GetIt packages, custom VCL components, and compiled libraries that may not be tracked by conventional SCA tools. [derscanner-delphi-sbom]

Legacy Delphi applications may have dependencies that were installed through non-standard processes, making manual dependency inventories incomplete and unreliable. [derscanner-delphi-sbom]

GetIt packages may include pre-compiled binaries and custom installers that obscure the true dependency graph, requiring analysis that goes beyond text-based manifest parsing. [derscanner-delphi-sbom]

SBOM accuracy depends on source-file resolution; compiled dependencies without source access may result in incomplete or inaccurate SBOM entries. [derscanner-delphi-sbom]

Security controls

Each control inspects a different artifact and produces evidence for an engineering decision.

Delphi project analysis

SCA-based SBOM generation
Artifact
Delphi project files, package configurations, and installed component directories.
Risk
Incomplete SBOMs that miss GetIt packages, custom VCL components, or system libraries due to reliance on standard manifest parsing alone.
Output
An SBOM of discovered components documenting component names, versions, and sources, including GetIt packages and framework components.

Evidence: DerScanner Delphi SBOM generation

Source-file resolution

SBOM accuracy validation
Artifact
Mapping between compiled dependencies and their original source files or package manifests.
Risk
SBOM entries that cannot be verified against source code or package metadata, reducing confidence in vulnerability assessment.
Output
Resolved source references for each SBOM entry, enabling accurate vulnerability matching and compliance evidence.

Evidence: DerScanner Delphi SBOM generation

Verification workflow

  1. Collect all Delphi project files, including project files, package files, and any custom component packages.
  2. Run SCA analysis that understands Delphi project file formats to discover all declared and transitive dependencies.
  3. Resolve GetIt packages by analyzing Delphi's package manager configuration and installed component directories.
  4. Map system libraries and VCL/FMX framework components to their versions and sources.
  5. Generate the SBOM in a standard format (SPDX or CycloneDX) documenting all discovered components.
  6. Validate SBOM accuracy by cross-referencing compiled dependencies against source-file resolution where available.
  7. Integrate SBOM generation into the build process to keep the inventory current as dependencies change.

Limits of verification

  • SBOM accuracy is limited by the availability of source files; compiled-only dependencies may not be fully resolved.
  • GetIt packages with custom installers may not be fully discoverable without manual review.
  • Legacy Delphi projects with decades of accumulated dependencies may have undocumented or obscure component relationships.
  • SBOM generation covers dependencies that DerScanner can analyze; some proprietary or obfuscated components may not be fully inventoried.

Canonical terms used: Software Bill of Materials; Delphi; GetIt package manager; SCA-based SBOM generation; Source-file resolution.

Evidence and references

  1. DerScanner Delphi SBOM generationDerScanner generates SBOMs for Delphi applications, with DerScanner 13 improving source-file resolution and handling of GetIt and system libraries.derscanner-delphi-sbom
  2. NIST SP 800-161 Rev. 1 — Supply Chain Risk ManagementOrganizations should maintain SBOMs as part of supply chain risk management practices to enable vulnerability assessment and incident response.nist-sbom-framework

Generate Delphi SBOMs

Create accurate SBOMs for your Delphi applications with automated SCA analysis.

Tell us about your Delphi projects, GetIt package usage, and dependency management challenges. The DerScanner team will help map SBOM generation to your development workflow.

Generate Delphi SBOMs

Discuss SBOM generation for your Delphi applications

Share your Delphi project details and dependency management requirements. We will respond with the next practical step for automated SBOM generation.

Engineering knowledge for building and operating trustworthy systems.

DerSecur Recognition · build 69d6783 · 2026-08-09 13:45:30Z · system