Skip to content
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 #423

Open
aponcedeleonch opened this issue Dec 19, 2024 · 1 comment

Comments

@aponcedeleonch
Copy link
Contributor

aponcedeleonch commented Dec 19, 2024

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.

@lukehinds
Copy link
Contributor

defer until after #454

@aponcedeleonch aponcedeleonch changed the title Track the filepath where the secret came from Track the filepath where the secret and malicious/archived packages came from Jan 15, 2025
@aponcedeleonch aponcedeleonch changed the title Track the filepath where the secret and malicious/archived packages came from Track the filepath where the secret and malicious/archived packages come from Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants