CT Log Metadata json endpoint

Open
#838 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go
Domain
api

Research direction

Start by reading the linked Google design document and the ct-policy thread to understand the log metadata JSON format and endpoint requirements. Then locate TesseraCT's Static CT API entry points and determine how the endpoint should expose that format. Done means the implementation supports the agreed metadata JSON contract, with tests covering the endpoint behavior.

Written by the indexing model from the issue text.

Description

enhancement

The ecosystem is moving towards log metadata jsons, designed in this google doc and ct-policy thread.

TesseraCT should support this.

Dominant language
Go
Stars
37
Forks
18
Avg merge
19h 22m
Merged PRs (30d)
15

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 transparency-dev/tesseract

All issues in transparency-dev/tesseract

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.