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

Normative: add attestation to terms?

Closed Beginner friendly
  • Is something wrong?
#351 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The issue points to a specific line in tea-collection.md. Open that file, locate clause 4.1, and add the definition of 'attestation' from line 146, changing 'statements' to 'statement' as instructed. Verify the change aligns with surrounding definitions and commit.

Written by the indexing model from the issue text.

Description

https://github.com/CycloneDX/transparency-exchange-api/blob/f5817aa0476b2240df068856dc92de7a9499efeb/tea-collection/tea-collection.md?plain=1#L146

this is a good definition, consider adding to clause 4.1 (s/statements/statement)

Dominant language
Shell
Stars
121
Forks
24
Avg merge
1d 15h
Merged PRs (30d)
41

Getting set up

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.