fix(opensearch-dashboards): Generate the SBOM from the built distribution - #1663
Merged
Merged
Conversation
StefanFl
approved these changes
Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Follow-up to #1630 and #1635. Those fixed the ecosystem over-detection (
--type js) and the vector feature set, which removed many components from the OpenSearch Dashboards SBOM, but the npm part was unchanged. The image SBOM still reported dev dependencies like Cypress or Selenium WebDriver, which are not part of the image.cdxgenran in the patched source worktree, which is a full development install. The resulting SBOM was the union of everydependenciesanddevDependenciesof the root project and all 15 plugin repositories.It now runs against the built distribution in
/stackable/opensearch-dashboards, which contains exactly what is shipped.This makes cdxgen walk the installed
node_modulesinstead of the lockfiles, which also closes the license gap (an installedpackage.jsonrecords a license while a Yarn 1 lockfile does not).Verified by building 3.4.0 locally and running the image SBOM steps from our CI pipeline.
Definition of Done Checklist
Note
Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant.
Please make sure all these things are done and tick the boxes
TIP: Running integration tests with a new product image
The image can be built and uploaded to the kind cluster with the following commands:
See the output of
boilto retrieve the image manifest URI for<MANIFEST_URI>.