Rule may-have-info-x-api-type invalid x-api-type value reports info with guidance ‑ Rule may-have-info-x-api-type invalid x-api-type value reports info with guidance
Rule may-have-info-x-api-type missing x-api-type reports info and assumes standard ‑ Rule may-have-info-x-api-type missing x-api-type reports info and assumes standard
Rule may-have-info-x-api-type valid x-api-type pygeoapi passes ‑ Rule may-have-info-x-api-type valid x-api-type pygeoapi passes
Rule may-have-info-x-api-type valid x-api-type standard passes ‑ Rule may-have-info-x-api-type valid x-api-type standard passes
Rule override-severity-pygeoapi, must-use-https-protocol-only pygeoapi: must-use-https-protocol-only downgraded to warn by override-severity-pygeoapi ‑ Rule override-severity-pygeoapi, must-use-https-protocol-only pygeoapi: must-use-https-protocol-only downgraded to warn by override-severity-pygeoapi
Rule override-severity-pygeoapi, must-use-https-protocol-only x-api-type standard: must-use-https-protocol-only enforced ‑ Rule override-severity-pygeoapi, must-use-https-protocol-only x-api-type standard: must-use-https-protocol-only enforced
Rule should-have-info-x-contains-sensitive-data invalid: info.x-contains-sensitive-data missing ‑ Rule should-have-info-x-contains-sensitive-data invalid: info.x-contains-sensitive-data missing
Rule should-have-info-x-contains-sensitive-data invalid: info.x-contains-sensitive-data wrong type (string) ‑ Rule should-have-info-x-contains-sensitive-data invalid: info.x-contains-sensitive-data wrong type (string)
Rule should-have-info-x-contains-sensitive-data valid: info.x-contains-sensitive-data present and boolean ‑ Rule should-have-info-x-contains-sensitive-data valid: info.x-contains-sensitive-data present and boolean
getLintTargets given no field, returns the whole input ‑ getLintTargets given no field, returns the whole input
getLintTargets when @key is given as field given array, returns its indicies ‑ getLintTargets when @key is given as field given array, returns its indicies
getLintTargets when @key is given as field given object, returns its keys ‑ getLintTargets when @key is given as field given object, returns its keys
getLintTargets when @key is given as field given primitive property, returns the whole input ‑ getLintTargets when @key is given as field given primitive property, returns the whole input
getLintTargets when JSON Path expression is given as field given existing property, returns lint targets ‑ getLintTargets when JSON Path expression is given as field given existing property, returns lint targets
getLintTargets when JSON Path expression is given as field given non-existing property, returns lint target with undefined value ‑ getLintTargets when JSON Path expression is given as field given non-existing property, returns lint target with undefined value
getLintTargets when JSON Path expression is given as field given primitive property, returns the whole input ‑ getLintTargets when JSON Path expression is given as field given primitive property, returns the whole input
getLintTargets when property path is given as field given existing property, returns lint targets ‑ getLintTargets when property path is given as field given existing property, returns lint targets
getLintTargets when property path is given as field given non-existing property, returns lint target with undefined value ‑ getLintTargets when property path is given as field given non-existing property, returns lint target with undefined value
getLintTargets when property path is given as field given primitive property, returns the whole input ‑ getLintTargets when property path is given as field given primitive property, returns the whole input
has-required-problem-details-error-responses fails gracefully when content of a response is not an object ‑ has-required-problem-details-error-responses fails gracefully when content of a response is not an object
has-required-problem-details-error-responses fails gracefully when response structure is not an object ‑ has-required-problem-details-error-responses fails gracefully when response structure is not an object
has-required-problem-details-error-responses fails gracefully when responses object is missing entirely ‑ has-required-problem-details-error-responses fails gracefully when responses object is missing entirely
has-required-problem-details-error-responses fails when 400 response is completely missing ‑ has-required-problem-details-error-responses fails when 400 response is completely missing
has-required-problem-details-error-responses fails when 401 and 403 are missing and security is enabled ‑ has-required-problem-details-error-responses fails when 401 and 403 are missing and security is enabled
has-required-problem-details-error-responses fails when 500 is missing example ‑ has-required-problem-details-error-responses fails when 500 is missing example
has-required-problem-details-error-responses fails when a response object is completely missing for a secured status ‑ has-required-problem-details-error-responses fails when a response object is completely missing for a secured status
has-required-problem-details-error-responses fails when a status code exists but response content is entirely missing ‑ has-required-problem-details-error-responses fails when a status code exists but response content is entirely missing
has-required-problem-details-error-responses fails when media type is present but missing both application/problem+json and application/problem+xml ‑ has-required-problem-details-error-responses fails when media type is present but missing both application/problem+json and application/problem+xml
has-required-problem-details-error-responses fails when response has correct media type but no examples ‑ has-required-problem-details-error-responses fails when response has correct media type but no examples
has-required-problem-details-error-responses passes when all required error responses are valid and security is enabled ‑ has-required-problem-details-error-responses passes when all required error responses are valid and security is enabled
has-required-problem-details-error-responses passes when root-inherit mode detects inherited global security ‑ has-required-problem-details-error-responses passes when root-inherit mode detects inherited global security
has-required-problem-details-error-responses passes when security is disabled and 401/403 are missing ‑ has-required-problem-details-error-responses passes when security is disabled and 401/403 are missing
has-required-problem-details-error-responses skips validation when mode is not specified ‑ has-required-problem-details-error-responses skips validation when mode is not specified
is-api-info-json-schema fails when documentation and releaseNotes formats are missing ‑ is-api-info-json-schema fails when documentation and releaseNotes formats are missing
is-api-info-json-schema fails when name is missing or invalid ‑ is-api-info-json-schema fails when name is missing or invalid
is-api-info-json-schema fails when pattern is defined but invalid ‑ is-api-info-json-schema fails when pattern is defined but invalid
is-api-info-json-schema fails when releaseDate is missing format ‑ is-api-info-json-schema fails when releaseDate is missing format
is-api-info-json-schema fails when schema is null ‑ is-api-info-json-schema fails when schema is null
is-api-info-json-schema fails when status enum is invalid or missing ‑ is-api-info-json-schema fails when status enum is invalid or missing
is-api-info-json-schema fails when version is missing semver pattern ‑ is-api-info-json-schema fails when version is missing semver pattern
is-api-info-json-schema fails when x-extensible-enum is missing entirely ‑ is-api-info-json-schema fails when x-extensible-enum is missing entirely
is-api-info-json-schema passes with a fully valid ApiInfo schema ‑ is-api-info-json-schema passes with a fully valid ApiInfo schema
is-api-info-json-schema skips validation if schema is not an object ‑ is-api-info-json-schema skips validation if schema is not an object
is-problem-json-schema fails when "type" is missing format ‑ is-problem-json-schema fails when "type" is missing format
is-problem-json-schema fails when all required fields are completely missing ‑ is-problem-json-schema fails when all required fields are completely missing
is-problem-json-schema fails when detail or instance are not strings ‑ is-problem-json-schema fails when detail or instance are not strings
is-problem-json-schema fails when status is not integer or wrong format ‑ is-problem-json-schema fails when status is not integer or wrong format
is-problem-json-schema fails when top-level type is not object ‑ is-problem-json-schema fails when top-level type is not object
is-problem-json-schema gracefully handles unexpected errors ‑ is-problem-json-schema gracefully handles unexpected errors
is-problem-json-schema handles combined schemas (anyOf) ‑ is-problem-json-schema handles combined schemas (anyOf)
is-problem-json-schema passes with a fully valid Problem schema ‑ is-problem-json-schema passes with a fully valid Problem schema
overrideSeverity target option downgrades severities when a JSONPath selector matches ‑ overrideSeverity target option downgrades severities when a JSONPath selector matches
overrideSeverity target option falls back to a generic label when target selector is empty ‑ overrideSeverity target option falls back to a generic label when target selector is empty
overrideSeverity target option handles numeric severity values and non-string messages ‑ overrideSeverity target option handles numeric severity values and non-string messages
overrideSeverity target option leaves severities unchanged when the selector does not match ‑ overrideSeverity target option leaves severities unchanged when the selector does not match
overrideSeverity target option leaves severity untouched when JSONPath matches nothing ‑ overrideSeverity target option leaves severity untouched when JSONPath matches nothing
overrideSeverity target option supports @key selectors when matching the configured value ‑ overrideSeverity target option supports @key selectors when matching the configured value
ruleset file exists ‑ ruleset file exists