Jan Kowalleck

the use of this lib in general is a good idea, but a better idea is: 1. split this project into several pieces: one for npm, one foe yarn, ......

:exclamation: :exclamation: #321 kind of contradicts this very issue, as it will cause this project to have no business logic at all, but big a wrapper.

this issue is related to `read-installed`. so #215 is blocking it.

this feature was implemented in the NPM flavour of this package: https://github.com/CycloneDX/cyclonedx-node-npm/

@CompartMSL please review my adaptations. unfortunately i was unable to reproduce the mentioned issues from #255

Thanks for the report @CompartMSL , could you setup a repository that showcases the issue? OR create a pullrequest with a test for that, like the integration tests here: https://github.com/CycloneDX/cyclonedx-node-module/blob/master/tests/index.test.js...

The issue could be caused upstream from https://www.npmjs.com/package/xmlbuilder please report it there, and link it to this very issue here. Thanks in advance, @CompartMSL

this one might cause other issues. see https://github.com/CycloneDX/cyclonedx-node-module/issues?q=is%3Aissue+is%3Aopen+read-installed

onhold, until https://github.com/CycloneDX/cyclonedx-node-module/pull/217 is done and all needed CI/CT improvements were incorporated, to be sure to release a well-tested version. --- PS: all done, ready to go

is this related to #300 ?