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

Flagging supply-chain security issues #372

Open
gabibguti opened this issue Jul 7, 2023 · 3 comments · May be fixed by #396
Open

Flagging supply-chain security issues #372

gabibguti opened this issue Jul 7, 2023 · 3 comments · May be fixed by #396

Comments

@gabibguti
Copy link
Contributor

Flagging supply-chain security issues is important for you to be aware of where your repository is vulnerable to these attacks and act upon it. Supply-chain attacks aim for your development, build and release weaknesses. That's why using minimum permissions for actions and referencing actions by commit SHA on your GitHub workflows helps protecting you from malicious actions on GitHub, specially in build and release workflows.

In this repository, we have already worked to flag and fix a few supply-chain security issues. To flag more issues like that, you can use Scorecard security tool to receive alerts in GitHub's Security Dashboard. If you agree, I can open a PR to add it.

Additional Context

Hi again! I'm Gabriela and I work on behalf of Google and the OpenSSF suggesting supply-chain security changes :)

@KodrAus
Copy link
Member

KodrAus commented Jul 31, 2023

Hi @gabibguti! 👋 I'm not familiar with Scorecard so would be keen to look into it. Is this the project here?

@gabibguti
Copy link
Contributor Author

Yes, that's it.

@gabibguti
Copy link
Contributor Author

Hi! Friendly ping here. Did you have time to look into Scorecard?

@KodrAus KodrAus linked a pull request Feb 1, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants