Normalize OWASP cheat sheet references#865
Open
Bornunique911 wants to merge 6 commits intoOWASP:mainfrom
Open
Conversation
Author
Author
|
Requesting kind reviews and feedback for this feature from : @northdpole , @Pa04rth , @robvanderveer |
ef1baee to
901c9a0
Compare
901c9a0 to
8df31e9
Compare
10585d9 to
38051c9
Compare
This was referenced Apr 24, 2026
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
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.


Summary
This PR addresses part of issue #471 by normalizing OWASP cheat sheet references used by the OWASP resource mapping flow.
This is the third upstream PR in the stacked #471 review series.
Problem Fixed
Cheat sheet references were inconsistent, which made later mapping and analysis less reliable.
Solution
Normalized cheat sheet references and updated parser expectations/tests.
Tests
Why this is split out
The full #471 work is too large to review effectively as one PR.
This PR isolates one OWASP resource family so the parser/data model can be reviewed independently before the later Kubernetes, cheat sheet, backend analysis, and frontend changes.