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

USECASE: Third Party Aggregator

Open
  • Is something wrong?
#202 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api, backend-api-design

Research direction

Review the existing API and the list of TEA use cases first, focusing on the stated need for bulk exports and “changed since” queries. Clarify the aggregator, offline-cache, and backup requirements, then determine how the API should address conflicting or falsely propagated artefacts. Done requires an agreed specification rather than an implementation inferred from this issue alone.

Written by the indexing model from the issue text.

Description

enhancement wontfix

In the list of TEA use cases, I see a gap where third party aggregators may want to generate an offline cache or a backup of documents. For example, some systems collect caches of CVEs by using dedicated APIs to pull batches of records. Some people may devise additional methods for deep analysis that require custom data stores, or that would otherwise tax the remote system. Other groups may want to create backups to prevent data loss due to disasters or the source provider "pulling the plug."

While the API as it exists allows for a smart system to query for all the data, I do not think it allows for efficient bulk exports, or for data updates in the form of "changed since" queries.

Note that, regardless of the implementation (or lack of implementation) for this functionality, it raises the spectre of how to handle false propagation of artefacts - one storehouse hosting contrasting information on a product than a different storehouse.

Dominant language
Shell
Stars
116
Forks
23
Avg merge
1d 3h
Merged PRs (30d)
58

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.