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

Bring back Artifact author to the Spec

Open
#149 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
api

Research direction

Inspect the specification definitions for the Artifact and Collection objects, then compare them with commit a7391972ad7c59572e1a47681aeb2ec5ebe380d1. Done means the Artifact object includes the author field while the Collection object does not.

Written by the indexing model from the issue text.

Description

Prio 2 TEA Artifact

Looks like the author field has been removed from the Artifact object, while it only needed to be removed from the Collection object.

Ref: https://github.com/CycloneDX/transparency-exchange-api/commit/a7391972ad7c59572e1a47681aeb2ec5ebe380d1

This should be re-introduced in the Artifact object.

Dominant language
Shell
Stars
116
Forks
23
Avg merge
2d 11h
Merged PRs (30d)
63

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/transparency-exchange-api

All issues in CycloneDX/transparency-exchange-api

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.