Open markusmuellerusi opened 4 months ago
Thanks a lot for providing issue details, this is indeed something we missed out in the inital implementation.
Expected behavior Please see cyclonedx-npm.json. The dependencies are generated. [...]
In the SBOM result, I would expect to not see the same dependency graph like it is generated by cyclonedx-npm
, instead I would expect the SBOM result to only include the things that are actually bundled by rollup - after tree-shaking.
And this should also affect the dependency graph.
Just saying. :-)
@janbiasi i would consider this as a feature request, not a bug ;-)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
When will a fix be available? Thanks in advance
When will a fix be available? Thanks in advance
Hey @markusmuellerusi
I was enjoying a longer vacation. I've already started working on this feature (not a bug as @jkowalleck mentioned) before - see PR https://github.com/janbiasi/rollup-plugin-sbom/pull/89 - however I can't tell you an exact estimate for that feature as it still requires some work.
In case you're willing to contribute, a PR is also very welcome :)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Describe the bug Dependencies are important to display the dependency graph i.e. in Dependency-Track. I attached two sbom files. rollup-plugin-sbom.json is created using plugin cyclonedx-npm.json is created from cli with npx @cyclonedx/cyclonedx-npm
The plugin doesn't generate any dependencies, all dependsOn nodes are missing:
To Reproduce Steps to reproduce the behavior Create the two sboms with plugin and and cli compare the boms
Expected behavior Please see cyclonedx-npm.json. The dependencies are generated.
Environment (please complete the following information):
Additional context
package.json:
vite.config.js: