Add registered prompt and gemini md updates for enabling notation usa… #107
+57
−0
Conversation
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
QuinnDACollins
requested review from
QuanZhang-William,
capachino,
evanotero,
heltonduarte,
pedrour and
shrishabh
as code owners
capachino
reviewed
Nov 13, 2025
GEMINI.md
Outdated
| * **Example:** A piece of code might use a slightly older, but not yet broken, cryptographic algorithm for a non-sensitive, internal cache key. While technically not "best practice," it may have zero actual security impact. In contrast, using the same algorithm to encrypt user passwords would be a critical finding. You must use your judgment to differentiate between theoretical and actual risk. | ||
| ### 5. Whitelisting Vulnerabilities |
Collaborator
There was a problem hiding this comment.
nit: the accepted term now seems to be "Allowlist"
Contributor
There was a problem hiding this comment.
+1 - here and the filename below.
Collaborator
There was a problem hiding this comment.
Can you update these instructions to "Allowlisting"
shrishabh
reviewed
Nov 14, 2025
GEMINI.md
Outdated
| * **Example:** A piece of code might use a slightly older, but not yet broken, cryptographic algorithm for a non-sensitive, internal cache key. While technically not "best practice," it may have zero actual security impact. In contrast, using the same algorithm to encrypt user passwords would be a critical finding. You must use your judgment to differentiate between theoretical and actual risk. | ||
| ### 5. Whitelisting Vulnerabilities |
Contributor
There was a problem hiding this comment.
+1 - here and the filename below.
capachino
reviewed
Nov 17, 2025
shrishabh
approved these changes
Nov 22, 2025
capachino
reviewed
Dec 1, 2025
GEMINI.md
Outdated
| * **Example:** A piece of code might use a slightly older, but not yet broken, cryptographic algorithm for a non-sensitive, internal cache key. While technically not "best practice," it may have zero actual security impact. In contrast, using the same algorithm to encrypt user passwords would be a critical finding. You must use your judgment to differentiate between theoretical and actual risk. | ||
| ### 5. Whitelisting Vulnerabilities |
Collaborator
There was a problem hiding this comment.
Can you update these instructions to "Allowlisting"
Contributor
Author
|
Compared ~10+ repos using our benchmarking script with the new and old analyze toml. Found no signifigant token usage increases and no regressions in vulnerability detection. |
capachino
approved these changes
Dec 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Add tooling for persistent notations in extension. Current implementation supports vulnerability whitelisting.