Code signing policy
Free code signing provided by SignPath.io, certificate by SignPath Foundation
Releases of the Windows installer are signed under the following policy. The file that is signed is BomLens-Setup.exe. Each release is built from this repository by a workflow that runs on GitHub-hosted runners, and every signing request needs an approver’s manual approval before the file is signed.
Team roles
Section titled “Team roles”- Committers and reviewers: haksungjang
- Approvers: haksungjang
Committers can change the source without a separate review. Changes proposed by anyone who is not a committer are reviewed by a team member before they are merged. An approver decides, for each release, whether the installer is signed.
Privacy policy
Section titled “Privacy policy”BomLens runs on your machine. No feature of BomLens sends your source code, SBOMs or scan results to a server operated by this project, and BomLens has no telemetry or usage analytics. The scanner container reads what you point it at and writes its results to the folder you chose.
BomLens does contact other services, listed below. Where a request carries identifiers, the list says which ones.
Requests made by default
Section titled “Requests made by default”- Update check (desktop app). When it starts, the installed desktop app asks the GitHub releases API (
api.github.com) for the latest release and compares the version number. The request carries no data about you or your scans. GitHub receives it like any other web request, so it sees your IP address. A failed request is ignored, and the packaged app has no setting to turn the check off. - Scanner image. The scanner image is downloaded from
ghcr.iothe first time, and an image that is already present is refreshed in the background. A source scan also pulls the language images it needs fromghcr.io.SBOM_PULL=neverstops the downloads, andSBOM_IMAGE_TARinstalls the image from a file. - Vulnerability database. The security report uses Trivy, which downloads its vulnerability database (about 1.5 GB) during a scan and keeps it in the cache folder (
SBOM_TRIVY_CACHE). The matching against it runs inside the container.TRIVY_SKIP_DB_UPDATE=trueand a mounted database let a scan run offline, andTRIVY_DB_REPOSITORYpoints to a mirror. - Exploit signals. The security report looks up the CVE ids it found at FIRST.org (EPSS) and downloads the CISA known exploited vulnerabilities list (KEV). The CVE ids of the findings are the only identifiers sent.
SECURITY_ENRICH=falseturns both lookups off. - Go vulnerability database. The image holds a snapshot. A scan downloads a newer one from
vuln.go.devonly when the snapshot is older than 7 days (BOMLENS_GO_VULNDB_MAX_AGE_DAYS) and the scan is not offline. - Dependency resolution in source scans. Resolving the dependencies of a source project and reading crate licenses make the scan container request packages and package metadata from the package registries your project already uses.
FETCH_LICENSE=falseturns off the license lookups, and--detection staticreads lock files instead of building. - Web UI lookup. The CVE and package lookup screen in the web UI and the desktop app asks OSV.dev when you use it. It sends the advisory id, or the ecosystem, package name and version you typed.
EXTERNAL_LOOKUP=falseturns it off.
Requests made only when you turn a feature on
Section titled “Requests made only when you turn a feature on”--license-registryandSTALENESS_ENRICH=truesend the ecosystem, name and version of components to deps.dev.--resolve-purlsends the package identifiers found in the SBOM you submitted for checking to deps.dev. Namespaces listed inPURL_RESOLVE_IGNOREare left out.--identify-vendoredsends file fingerprints (hashes) of C and C++ source files to the SCANOSS OSSKB service. The files themselves are not sent.SCANOSS_API_URLpoints to another endpoint.--model <owner/name>and--resolve-modelsread model metadata from the Hugging Face hub, and--modelwith a Figshare item reads the item from the Figshare API. The web UI clones a repository address you enter for a source scan.--upload-target,--truscaand the web UI upload step send the finished SBOM to the Dependency-Track or TRUSCA server whose address (API_URL) you give.--deep-cve,--deep-licenseand the other opt-in images are pulled fromghcr.io.SECURITY_NVD_VERIFY=truealso queries the NVD API.
For the full option list, see the CLI reference, and for the design behind it, see Local-first by design.
Installation and removal
Section titled “Installation and removal”The Windows installer lets you choose the installation folder. The repository defines no custom installer steps, so BomLens makes no firewall or registry changes of its own. To remove BomLens, uninstall it from Windows Settings, then delete the settings folder %APPDATA%\sbom-generator-desktop if you want to remove the data the app kept. The scanner images stay in Docker until you remove them. For the commands, see the uninstall steps in the no-CLI quick start.
OWASP BomLens, an OWASP Incubator Project ·Contributing
Copyright © 2026 SK Telecom Co., Ltd. ·Apache-2.0 ·Third-party licenses