Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE]: Add a proper way to represent VCS tags

Open
#891 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet

Research direction

Start by inspecting how pedigree, commits, and the commit object are defined in the CycloneDX specification. Compare the proposed tags-on-commit representation with the alternative of tags alongside commits, including how a tag points to a specific commit. Done means the specification has a decided, documented representation for VCS tags.

Written by the indexing model from the issue text.

Description

proposed core enhancement

Describe the feature

Currently, there is no good way to represent version control tags.

Possible solutions

Suggestion is to add a new optional field with list of tags to the pedigree -> commits -> commit object.

Alternatives

It could be considered to add tags alongside commits, but then it won't be possible to represent tags pointing to a specific commit.

Dominant language
XSLT
Stars
551
Forks
93
Avg merge
4h 51m
Merged PRs (30d)
42

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CycloneDX/specification

All issues in CycloneDX/specification

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.