Sonatype Nexus · API Governance Rules

Sonatype Nexus API Rules

Spectral linting rules defining API design standards and conventions for Sonatype Nexus.

9 Rules error 2 warn 7
View Rules File View on GitHub

Rule Categories

nexus

Rules

warn
nexus-path-version-prefix
$.paths[*]~
warn
nexus-operation-summary-title-case
$.paths[*][*].summary
error
nexus-operation-id-required
$.paths[*][get,post,put,delete,patch]
warn
nexus-repository-path-param-naming
$.paths[*]~
warn
nexus-operation-tags-required
$.paths[*][get,post,put,delete,patch]
error
nexus-security-schemes-defined
$.components.securitySchemes
warn
nexus-success-response-required
$.paths[*][get,post,put,delete,patch].responses
warn
nexus-info-contact-required
$.info
warn
nexus-no-trailing-slash
$.paths[*]~

Spectral Ruleset

Raw ↑
extends: spectral:oas
rules:

  # Nexus Repository API uses /v1/ and /beta/ versioning prefixes
  nexus-path-version-prefix:
    message: "Paths must start with /v1/ or /beta/"
    severity: warn
    given: "$.paths[*]~"
    then:
      function: pattern
      functionOptions:
        match: "^/(v1|beta)/"

  # All operation summaries should use Title Case
  nexus-operation-summary-title-case:
    message: "Operation summaries should use Title Case"
    severity: warn
    given: "$.paths[*][*].summary"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z]"

  # All operations should have an operationId
  nexus-operation-id-required:
    message: "Operations must have an operationId"
    severity: error
    given: "$.paths[*][get,post,put,delete,patch]"
    then:
      field: operationId
      function: truthy

  # Repository name path parameters should use {repositoryName} or {name}
  nexus-repository-path-param-naming:
    message: "Repository path parameters should be {repositoryName} or {name}"
    severity: warn
    given: "$.paths[*]~"
    then:
      function: pattern
      functionOptions:
        notMatch: "\\{repo\\}|\\{repository\\}|\\{repoName\\}"

  # Operations must have at least one tag
  nexus-operation-tags-required:
    message: "Operations must have at least one tag"
    severity: warn
    given: "$.paths[*][get,post,put,delete,patch]"
    then:
      field: tags
      function: truthy

  # API must define security schemes
  nexus-security-schemes-defined:
    message: "API must define security schemes (BasicAuth)"
    severity: error
    given: "$.components.securitySchemes"
    then:
      function: truthy

  # Responses must document at least a 2xx response
  nexus-success-response-required:
    message: "Operations must document at least one success response"
    severity: warn
    given: "$.paths[*][get,post,put,delete,patch].responses"
    then:
      function: schema
      functionOptions:
        schema:
          anyOf:
            - required: ["200"]
            - required: ["201"]
            - required: ["204"]

  # Info must have contact
  nexus-info-contact-required:
    message: "API info must have a contact field"
    severity: warn
    given: "$.info"
    then:
      field: contact
      function: truthy

  # No trailing slashes on paths
  nexus-no-trailing-slash:
    message: "Paths must not end with a trailing slash"
    severity: warn
    given: "$.paths[*]~"
    then:
      function: pattern
      functionOptions:
        notMatch: "/$"

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/sonatype-nexus-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.