Sigstore · Schema

Sigstore Rekor Log Entry

Schema representing an entry in the Sigstore Rekor transparency log.

Certificate AuthorityCode SigningContainersCryptographyOpen-SourcePKISecuritySoftware Supply ChainTransparency Log

Properties

Name Type Description
uuid string The UUID of the log entry.
body string Base64-encoded entry content containing the signed artifact metadata.
integratedTime integer Unix timestamp (seconds) when the entry was integrated into the log.
logID string SHA256 hash of the log's public key, identifying which log holds this entry.
logIndex integer The index of this entry in the transparency log.
verification object Proof of inclusion data for this log entry.
View JSON Schema on GitHub

JSON Schema

sigstore-log-entry-schema.json Raw ↑
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/sigstore/refs/heads/main/json-schema/sigstore-log-entry-schema.json",
  "title": "Sigstore Rekor Log Entry",
  "description": "Schema representing an entry in the Sigstore Rekor transparency log.",
  "type": "object",
  "properties": {
    "uuid": {
      "type": "string",
      "description": "The UUID of the log entry."
    },
    "body": {
      "type": "string",
      "description": "Base64-encoded entry content containing the signed artifact metadata."
    },
    "integratedTime": {
      "type": "integer",
      "description": "Unix timestamp (seconds) when the entry was integrated into the log."
    },
    "logID": {
      "type": "string",
      "description": "SHA256 hash of the log's public key, identifying which log holds this entry."
    },
    "logIndex": {
      "type": "integer",
      "description": "The index of this entry in the transparency log."
    },
    "verification": {
      "type": "object",
      "description": "Proof of inclusion data for this log entry.",
      "properties": {
        "inclusionProof": {
          "type": "object",
          "description": "Merkle tree inclusion proof for verifying this entry is in the log.",
          "properties": {
            "checkpoint": {
              "type": "string",
              "description": "Signed tree head (checkpoint) at the time of inclusion."
            },
            "hashes": {
              "type": "array",
              "description": "List of SHA256 hashes forming the inclusion proof path.",
              "items": {
                "type": "string"
              }
            },
            "logIndex": {
              "type": "integer",
              "description": "The log index of this entry."
            },
            "rootHash": {
              "type": "string",
              "description": "The Merkle tree root hash at time of inclusion."
            },
            "treeSize": {
              "type": "integer",
              "description": "The tree size at time of inclusion."
            }
          }
        },
        "signedEntryTimestamp": {
          "type": "string",
          "description": "Signed Entry Timestamp (SET) — the log's signature over the entry and timestamp."
        }
      }
    }
  },
  "required": ["body", "integratedTime", "logID", "logIndex"]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/sigstore-log-entry"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.