Surface OWASP resource mappings in explorer and analysis UI for issue#16
Open
Bornunique911 wants to merge 5 commits into
Open
Conversation
30d6b06 to
da8944f
Compare
9fd1a4e to
e16caa4
Compare
6765ed2 to
bb1c422
Compare
2d4514e to
7f0850c
Compare
bb1c422 to
4d48af6
Compare
7f0850c to
0da3813
Compare
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 adds the main frontend/UI layer for surfacing the OWASP standards and analysis behavior introduced by the earlier backend PRs.
It now also includes the core popup-rendering fix for map-analysis hover behavior, so the primary frontend review does not depend on a later follow-up branch for correct standard/CRE traversal.
What changed
Why this is split out
This branch is the main frontend layer on top of the backend analysis stack.
It intentionally includes the generic frontend behavior fixes that should apply broadly across the
#471analysis work. Kubernetes-specific comparison behavior remains in a later follow-up branch so this PR stays focused on the shared frontend layer.Validation
Validated as the frontend delta relative to
review/issue-471-analysis-specialized.