Stellar Cyber · API Governance Rules
Stellar Cyber API Rules
Spectral linting rules defining API design standards and conventions for Stellar Cyber.
11 Rules
error 3
warn 8
Rule Categories
stellar
Rules
warn
stellar-cyber-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][*].summary
warn
stellar-cyber-operation-id-kebab-case
OperationIds should use camelCase
$.paths[*][*].operationId
error
stellar-cyber-tags-required
All operations must have at least one tag
$.paths[*][*]
error
stellar-cyber-response-200-required
All GET operations must return a 200 response
$.paths[*].get
warn
stellar-cyber-security-defined
All operations should have security requirements defined
$.paths[*][*]
error
stellar-cyber-bearer-auth-only
Stellar Cyber uses JWT Bearer authentication exclusively
$.components.securitySchemes
warn
stellar-cyber-path-kebab-case
URL path segments must use kebab-case
$.paths
warn
stellar-cyber-request-body-described
Request bodies on POST/PUT operations should have descriptions
$.paths[*][post,put].requestBody
warn
stellar-cyber-parameters-have-descriptions
All parameters should have descriptions
$.paths[*][*].parameters[*]
warn
stellar-cyber-no-empty-descriptions
Descriptions must not be empty
$..[description]
warn
stellar-cyber-4xx-responses
Operations should define 401 unauthorized response
$.paths[*][*].responses