Conversation
Assisted-By: devx/6a87267f-002b-45a7-a964-2b150210ff87
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.
WHY are these changes introduced?
The OAuth-scope prompt treats missing local API references as evidence of excessive access. That can flag planned features, optional scopes, generated queries, and usage outside the reviewed directory without establishing a security problem. It also conflates local scope declarations with effective grants and unauthorized API access.
WHAT is this pull request doing?
Require concrete excess-authority evidence for
SCOPE_OVER_REQUESTfindings. Trace supported feature paths and exact API scope requirements, distinguish declared/requested/granted access, and keep incomplete evidence unresolved. Least-privilege cleanup remains useful guidance without automatically becoming a high-severity finding.Update the versioned prompt, catalog guidance, and embedded source. This is independent of the route-auth cutover and #8591; it does not change finding or trace schemas.
How to manually test your changes?
Checklist