CycloneDX / CycloneDX/cyclonedx-python

feat!: dont "fix" licenses if not needed.

未关闭
#995 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
breaking change enhancement schema 1.7
主要语言
Python
星标
390
派生
98
平均合并
2 天 23 小时
30 天内合并 PR
2

描述

currently, we "fix" licenses
> """
> Per CycloneDX spec, there must be EITHER one license expression OR multiple license id/name.
> If there is an expression, it is used and everything else is moved to evidences, so it is not lost.
> """
> # hack for preventing expressions AND named licenses.
> # see https://github.com/CycloneDX/cyclonedx-python/issues/826
> # see https://github.com/CycloneDX/specification/issues/454

see https://github.com/CycloneDX/cyclonedx-python/blob/ffe63d1f5524c0d4b5788e282bf0d108b688017b/cyclonedx_py/_internal/utils/cdx.py#L102-L119

this is no longer needed since CycloneDX 1.7

feature request: dont "fix" licenses if not needed.

this might be considered a breaking change, since the output result might be different.

贡献指南

打开贡献指南

调研方向

Start with cyclonedx_py/_internal/utils/cdx.py around lines 102-119 and read the linked CycloneDX issues and specification context. Determine how CycloneDX 1.7 changes the license requirement, then verify that licenses are left unchanged when the compatibility fix is unnecessary. The completed change should account for the possible output change noted in the issue.

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
security, tooling
Issue 类型
功能
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。