transparency-dev / transparency-dev/tesseract
[Demand Signal] names API extension
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 37
- Forks
- 18
- Avg merge
- 19h 22m
- Merged PRs (30d)
- 15
Description
At the moment, TesseraCT does not support a name/ endpoint as described on ct-policy.
This issue is meant to track user demand, such that we can prioritize accordingly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked ct-policy discussion to understand the proposed name/ endpoint and its expected behavior. This issue names no files, tests, or implementation entry point, and its completion criteria are not defined beyond tracking demand, so further project guidance is needed before work can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100