Added LangSmith API Key detector #4251
Merged
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
nabeelalam
approved these changes
Jun 23, 2025
Comment on lines
+56
to
+58
| isVerified, verificationErr := verifyMatch(ctx, client, apiKey) | ||
| s1.Verified = isVerified | ||
| s1.SetVerificationError(verificationErr, apiKey) |
There was a problem hiding this comment.
Since the keys could be either a personal api token or service keys, how different could these keys be in terms of permissions/access? And is it worth storing this info in extra data?
There was a problem hiding this comment.
There is no fine grain access for these keys.
shahzadhaider1
approved these changes
Jun 23, 2025
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.
Description:
This PR adds a new detector for LangSmith API Keys
Tests:
Checklist:
make test-community)?make lintthis requires golangci-lint)?