harden-runner
action-semantic-pull-request
harden-runner | action-semantic-pull-request | |
---|---|---|
15 | 5 | |
503 | 849 | |
5.4% | - | |
7.1 | 4.8 | |
6 days ago | 9 days ago | |
TypeScript | JavaScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
harden-runner
-
Securizing your GitHub org
Fortunately there is a great free online tool that help you by doing all the hard work (it will open a pull-request and automatically fix issues).
- harden-runner: Protect your CI/CD pipeline from SolarWinds and Codecov-Type Attacks with the Harden-Runner Security Agent
- Show HN: Protect Your CI/CD from SolarWinds-Type Attacks with This Agent
-
Compromised PyTorch-nightly dependency chain December 30th, 2022
If using GitHub Actions for CI/ CD, Harden Runner (https://github.com/step-security/harden-runner) can be used to audit and block DNS exfiltration. Outbound calls from CI are predictable (to source repo, artifact registry, etc.) and don't change often.
-
Attack Simulator for SolarWinds, Codecov, and ua-parser-js breaches
As part of writing tests for Harden Runner GitHub Action, which prevents such attacks, there was a need to write attack simulator for these attacks.
-
py-template: one-click extensive GitHub Actions pipelines for your Python projects!
I am not too familiar with GitLab, to be honest, but: - Commit/PR linting (to be in tandem with semantic versioning) is implemented via third-party GitHub Actions (https://github.com/amannn/action-semantic-pull-request and https://github.com/wagoid/commitlint-github-action), these might be hard to transfer - Blocking egress to mitigate supply chain attacks is performed by step security’s Harden Runner (https://github.com/step-security/harden-runner), you may raise a question there about GitLab support - CodeQL support is GitHub only AFAIK (but you would have to verify it)
-
Securing a GitHub repo is a ton of work
I've found StepSecurity's tooling helpful in getting my repos secured.
* https://app.stepsecurity.io/securerepo
-
Sigstore
I agree. There are projects such as https://github.com/ossf/package-analysis and https://github.com/step-security/harden-runner that do behavior analysis. Disclaimer: I’m maintainer of the second one.
-
Best practices to keep your projects secure on GitHub
So if you are concerned about this, I'd suggest looking at the following:
* OpenSSF Scorecard Action - https://github.com/ossf/scorecard#scorecards-github-action
* Step Security Harden Action - https://github.com/step-security/harden-runner
I realize that this means trusting these providers but they seem at least tacitly blessed by GitHub. https://docs.github.com/en/actions/security-guides/security-...
-
Video of malware node packages trying to phone home
Few hours back several malicious packages were released on npm registry. This video shows how some of these packages are making outbound calls as part of the preinstall step when executed in a GitHub Actions workflow. DNS Exfiltration and network calls detected by Harden-Runner GitHub Action https://github.com/step-security/harden-runner
action-semantic-pull-request
-
How do you link commits to tickets ?
Here you go: https://github.com/amannn/action-semantic-pull-request
-
py-template: one-click extensive GitHub Actions pipelines for your Python projects!
I am not too familiar with GitLab, to be honest, but: - Commit/PR linting (to be in tandem with semantic versioning) is implemented via third-party GitHub Actions (https://github.com/amannn/action-semantic-pull-request and https://github.com/wagoid/commitlint-github-action), these might be hard to transfer - Blocking egress to mitigate supply chain attacks is performed by step security’s Harden Runner (https://github.com/step-security/harden-runner), you may raise a question there about GitLab support - CodeQL support is GitHub only AFAIK (but you would have to verify it)
-
Microservices Shared Libraries — Design and Best Practices
There are many great tools to help with automation here, some of them are action-semantic-pull-request to enforce conventional commits and standard version to bump the version and create a changelog according to the conventional commits.
-
How to Write a Great Git Commit Message
+1 on conventional commits (big fan)
also, +1 on fully paved road approach!
You might want to check out this GitHub Action to enforce PR title matches the spec: https://github.com/amannn/action-semantic-pull-request
-
How to lint PRs and welcome contributors using GitHub Actions
amannn/[email protected] - ensures pull request title matches conventional commits specification
What are some alternatives?
repo
conventional-commit - commit binary powered by commitizen with conventional commit standard
actual-malware - Useful library dependency
semantic-release - :package::rocket: Fully automated version management and package publishing
sigstore-website - Codebase for sigstore.dev
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
auth - A GitHub Action for authenticating to Google Cloud.
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
scorecard - OpenSSF Scorecard - Security health metrics for Open Source
commit-emoji - Performs a git commit with a random emoji message. 😂 🤙 🚀
github-actions-goat - GitHub Actions Goat: Deliberately Vulnerable GitHub Actions CI/CD Environment
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed