Sigstore · API Governance Rules

Sigstore API Rules

Spectral linting rules defining API design standards and conventions for Sigstore.

6 Rules error 1 warn 5
View Rules File View on GitHub

Rule Categories

sigstore

Rules

warn
sigstore-operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][*].summary
warn
sigstore-api-versioned-paths
All API paths must include a version prefix.
$.paths[*]~
warn
sigstore-tags-defined
Operations must include at least one tag.
$.paths[*][*]
error
sigstore-operationid-required
Every operation must have an operationId.
$.paths[*][*]
warn
sigstore-error-response
API operations should document error responses.
$.paths[*][*].responses
warn
sigstore-description-required
API info and operations must have descriptions.
$.info$.paths[*][*]

Spectral Ruleset

Raw ↑
extends: "spectral:oas"
rules:
  sigstore-operation-summary-title-case:
    description: Operation summaries must use Title Case.
    message: "Summary '{{value}}' must be in Title Case."
    severity: warn
    given: "$.paths[*][*].summary"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z][a-zA-Z0-9]*([ ][A-Z][a-zA-Z0-9]*)*$"

  sigstore-api-versioned-paths:
    description: All API paths must include a version prefix.
    message: "Path '{{property}}' should include a version segment (e.g., /api/v1/ or /api/v2/)."
    severity: warn
    given: "$.paths[*]~"
    then:
      function: pattern
      functionOptions:
        match: "^/api/v[0-9]+"

  sigstore-tags-defined:
    description: Operations must include at least one tag.
    message: "Operation is missing tags."
    severity: warn
    given: "$.paths[*][*]"
    then:
      field: tags
      function: truthy

  sigstore-operationid-required:
    description: Every operation must have an operationId.
    message: "Operation is missing an operationId."
    severity: error
    given: "$.paths[*][*]"
    then:
      field: operationId
      function: truthy

  sigstore-error-response:
    description: API operations should document error responses.
    message: "Operation should document at least one error response (4xx/5xx)."
    severity: warn
    given: "$.paths[*][*].responses"
    then:
      function: schema
      functionOptions:
        schema:
          type: object
          minProperties: 2

  sigstore-description-required:
    description: API info and operations must have descriptions.
    message: "{{property}} is missing a description."
    severity: warn
    given:
      - "$.info"
      - "$.paths[*][*]"
    then:
      field: description
      function: truthy

Work with this as data

Every ruleset 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 spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset 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 ruleset
curl "https://apis.io/api/v1/rules/sigstore-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?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.