-
Notifications
You must be signed in to change notification settings - Fork 5
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
Track the filepath where the secret and malicious/archived packages come from #386
Comments
defer until after stacklok/codegate#454 |
For secrets, I added code snippets to the alerts, so we can identify the path:
i will look at doing the same for packages |
When generating an alert for a malicious package, we can associate with the code snippet that brought it, and provide this info to the user Related-to: #423
When generating an alert for a malicious package, we can associate with the code snippet that brought it, and provide this info to the user Related-to: #423
I added codde snippets also to malicious packages. Now what's missing is to visualize that into the frontend |
Add a
CodeSnippet
object to the stored alerts for secrets and malicious/archived packages. This would enable to know from which file a specific secret came from.The text was updated successfully, but these errors were encountered: