-
Notifications
You must be signed in to change notification settings - Fork 649
Add API endpoint to receive alerts of exposed API tokens from GitHub #5495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ef20a89
to
2c285a7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a few minor comments, but this looks pretty good already. nice work!
btw I rebased and squashed the commits :)
Thanks for the feedback, I'll be working on that. |
☔ The latest upstream changes (presumably #5535) made this pull request unmergeable. Please resolve the merge conflicts. |
2c285a7
to
43f7796
Compare
c2ed6b3
to
da0d846
Compare
rebased once more due to |
da0d846
to
b742928
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
there are a few little improvements left, but those can be done in a follow-up PR :)
👋 I'm on the Secret Scanning team too. Just tested out the endpoint with some real API tokens, and things look good from our side! I received the email from crates.io as well! |
Adds a new POST endpoint at
/tokens/alert/github
to receive alerts from GitHub when crates.io API tokens are exposed.Requires adding a dependency on ring for ECDSA signature validation.
Intended to resolve #3400.