Synopsys · API Governance Rules
Synopsys API Rules
Spectral linting rules defining API design standards and conventions for Synopsys.
12 Rules
error 3
warn 7
info 2
Rule Categories
async
issue
operation
paths
polaris
report
scan
Rules
error
operation-operationId
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
error
operation-summary
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
operation-tags
All operations must be tagged.
$.paths[*][get,post,put,patch,delete]
warn
operation-description
All operations should have a description.
$.paths[*][get,post,put,patch,delete]
info
scan-response-issue-count
Scan completion responses should include issue count information.
$.components.schemas.Scan.properties
error
issue-severity-required
Issue schema must include a severity field.
$.components.schemas.Issue.properties
warn
issue-cwe-field
Issue schema should include a CWE reference field.
$.components.schemas.Issue.properties
info
polaris-content-type
Polaris API responses may use versioned vendor content types.
$.paths[*][*].responses[*].content
warn
async-operation-202
Operations that may be asynchronous must include a 202 response.
$.paths[*].post.responses
warn
paths-kebab-case
Path segments must use kebab-case.
$.paths
warn
report-format-required
Report request schema must include a format field.
$.components.schemas.ReportRequest.properties