Skip to content

[WIP] CycloneDX v2.0 Specification -- requirement schema #663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: 2.0-dev-threatmodeling
Choose a base branch
from

Conversation

anthonyharrison
Copy link

No description provided.

@anthonyharrison anthonyharrison requested a review from a team as a code owner July 23, 2025 12:35
Signed-off-by: anthonyharrison <[email protected]>
@anthonyharrison anthonyharrison force-pushed the 2.0-dev-threatmodeling branch from c152f47 to 9b07589 Compare July 23, 2025 12:36
@anthonyharrison anthonyharrison changed the title feat: requirement schema (WIP) [CylonedDX 2.0] feat: requirement schema (WIP) Jul 23, 2025
@anthonyharrison anthonyharrison changed the title [CylonedDX 2.0] feat: requirement schema (WIP) [CycloneDX 2.0] feat: requirement schema (WIP) Jul 23, 2025
@jkowalleck jkowalleck changed the title [CycloneDX 2.0] feat: requirement schema (WIP) [WIP] CycloneDX v2.0 Specification -- requirement schema Jul 23, 2025
@jkowalleck jkowalleck marked this pull request as draft July 23, 2025 18:08
@jkowalleck
Copy link
Member

jkowalleck commented Jul 23, 2025

A wild (draft) PR without any comment appears, without any comments.

whats the context? (I remember reading something about "requirements" in some slack channel recently)

PS: there is some conflict - see https://github.com/CycloneDX/specification/pull/663/conflicts

@anthonyharrison
Copy link
Author

Was discussed at today's TM-BOM meeting. It was produced for discussion.

An updated schema is now being produced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants