National University of Singapore · API Governance Rules
National University of Singapore API Rules
Spectral linting rules defining API design standards and conventions for National University of Singapore.
11 Rules
error 7
warn 4
Rule Categories
nus
Rules
error
nus-operator-declared
Every NUS contract must declare who operates the thing it describes.
$.info
error
nus-provenance-method
Every NUS contract must say how API Evangelist came to hold it.
$.info
error
nus-provenance-source
Derived contracts must name the live document they were derived from.
$.info
error
nus-servers-institution-host
An institution-operated contract must be served from a host under the institution's own registrable domain. This is the check that would have caught the Figshare misattribution.
$.servers[*].url
error
nus-operations-have-ids
Every operation needs a stable operationId for agents and code generators.
$.paths[*][get,put,post,delete,patch]
warn
nus-operations-described
Every operation needs a description, not just a summary.
$.paths[*][get,put,post,delete,patch]
error
nus-security-schemes-defined
A contract fronting a federated identity service must define its security schemes.
$.components
error
nus-token-endpoint-authenticated
The token endpoint must not be reachable with empty security.
$.paths['/adfs/oauth2/token/'].post
warn
nus-error-responses-present
Every operation should document at least one non-2xx response.
$.paths[*][get,put,post,delete,patch].responses
warn
nus-terms-of-service
A public contract should point at the terms the caller is bound by.
$.info
warn
nus-contact-present
A public contract should name a contact.
$.info