Repository navigation
Correct the industry-ruleset count: one standard, two rulesets - #11
Merged
Merged
Conversation
The published page named only Stoplight's OWASP ruleset and described the tier as served by nobody. It omitted api-commons/spectral-owasp-ruleset v0.2.0 — 22 checks across all ten OWASP categories, built-in functions only — which is the wrong omission for this page in particular to make, since API Commons publishes both the ruleset and the research. The argument is unchanged: one standard has coverage, and it is the same standard twice. The count was wrong and the conflict of interest went unstated. Both are now on the page, with a dated correction note. Retitles the page and the queued post, which both said "only one" of the rulesets rather than of the standards. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A correction to
/research/industry-rulesets/, published earlier today.What was wrong
The page said one industry ruleset exists — Stoplight's OWASP — and described the tier as served by nobody.
It omitted
api-commons/spectral-owasp-rulesetv0.2.0: 22 checks mapped across all ten OWASP API Security Top 10 (2023) categories, using only Spectral's built-in functions. Published on npm as@api-common/spectral-owasp-ruleset.That is the wrong omission for this page in particular to make, since API Commons publishes both the ruleset and the research arguing nobody serves the tier.
What changed
The argument is unchanged. One standard has coverage and it is the same standard twice; the other ninety-odd have none. If anything "two rulesets for one standard, and none for the rest" states the problem more sharply than the original.
The permalink is unchanged, so the links from
spotlight-spec#21and the alias post keep resolving.Notes