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

security: analyze dependencies for malicious behavior #87

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

varunsh-coder
Copy link

This PR

  1. Adds harden-runner GitHub Action to the workflow.
  2. Sets the token permission for the workflow to contents: read. This is a security best practice and gets you are higher Scorecard score. Your package currently has score of 4.5/10. You can use https://app.stepsecurity.io to automate some of the fixes, such as pinning actions to commit SHA...

harden-runner GitHub Action detects hijacked dependencies and compromised build tools. It correlates outbound traffic with each step of the workflow so you can see what processes are calling what endpoints. This is the analysis when run on a fork: https://app.stepsecurity.io/github/varunsh-coder/node.inflection/actions/runs/1928734058

You can restrict traffic to the allowed endpoints for future runs which will block calls that compromised dependencies typically make, and an annotation will be shown in such cases. You do not need to grant any permission or install any App to use this, and the action (and agent the action uses) are open source.

Information on how harden-runner could have detected past package hijacks can be found here: https://github.com/step-security/supply-chain-goat. Do share feedback to improve the harden-runner GitHub Action developer experience. Thanks!

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 this pull request may close these issues.

None yet

1 participant