CycloneDX / CycloneDX/guides

[CDX1.7] guide for "component.isExternal"

Open
#29 7 comments 0 reactions 0 assignees View on GitHub
help wanted t: MBOM t: OBOM t: SBOM t: VDR+VEX
Dominant language
CSS
Stars
9
Forks
12
Avg merge
12h 20m
Merged PRs (30d)
21

Description

based on https://github.com/CycloneDX/specification/issues/321

enhance the **SBOM** guide on when to mark compoennts as "isExternal".
- use cases are in the ticket
- section followup in the ticket
- additional questions are in https://github.com/CycloneDX/specification/pull/326 & https://github.com/CycloneDX/specification/pull/586

also discuss the following:
- transitive dependencies and hashes still make sense for external components -- as they may be version-pinned -> may also hash-pinned
- dont use component's "isExternal"/"versionRange" in **VEX/VDR** -- in this case we require specific versions
- dont use component's "isExternal"/"versionRange" in **OBOM** -- in this case all belongs to the system(universe)
make it clear in the OBOM guide, that there must not be any runtime components with a version range - it just makes no sense
- dont use component's "isExternal"/"versionRange" in **MBOM** -- in this case all belongs to the build system(universe)
make it clear in the MBOM guide, that there must not be any build-components with a version range - it just makes no sense

----

## Status
- [ ] MBOM
- [ ] OBOM
- [x] SBOM -
- [ ] VDR+VEX

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.