slsa-provenance-action
secure-repo
| slsa-provenance-action | secure-repo | |
|---|---|---|
| 1 | 6 | |
| 45 | 239 | |
| - | 2.5% | |
| 8.3 | 2.8 | |
| 4 days ago | about 2 months ago | |
| Go | Go | |
| MIT License | GNU Affero General Public License v3.0 |
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.
slsa-provenance-action
secure-repo
-
Show HN: Secure your public GitHub repository with automated security fixes
I am excited to share Secure-Repo, an open-source project that can easily secure your GitHub repository through automated security fixes. The project aims to automate common security fixes, so developers do not have to wade through documentation.
It does not require any App installation or onboarding steps, you can just enter your public repository and click on a button to improve security through automated pull requests.
I invite you to try Secure-Repo on your public repository using the hosted version at http://app.stepsecurity.io/securerepo and share your feedback.
Important open-source repositories have adopted the tool. Here are a few example pull requests created by the maintainers of Electron, Ruby, and GoogleCloudPlatform using this project.
Electron: https://github.com/electron/electron/pull/36363
-
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
-
Do you maintain a GitHub Action? Contribute to the SecureWorkflows project!
The problem we are trying to solve is to automatically calculate what the minimum GITHUB_TOKEN permissions should be for a given workflow. We are solving this problem by building a knowledge base of permissions needed by each GitHub Action. If you own a GitHub Action, contribute to the SecureWorkflows project by adding a YAML file describing the permissions your Action needs.
-
StepSecurity releases tool that it used to improve security of 30 critical open-source projects (including NodeJS, OpenSSL, Python, Rails, React Native)
List of merged pull requests for the 30 critical projects can be found here: https://github.com/step-security/secure-workflows/issues/462
- Secure GitHub Actions workflows by automatically updating the workflow (YAML) files
What are some alternatives?
in-toto-golang - A Go implementation of in-toto. in-toto is a framework to protect software supply chain integrity.
machine - Machine is a workflow/pipeline library for processing data
slsa-github-generator - Language-agnostic SLSA provenance generation for Github Actions
DnsControl - Infrastructure as code for DNS!
paste-secret - Paste your GitHub Secrets to files
Beehive - A flexible event/agent & automation system with lots of bees 🐝
action - GitHub action to supercharge your pull request and issues workflows!
reposaur - Open source compliance tool for development platforms.
mysql-actions - MySQL Actions
functions-framework-dotnet - FaaS (Function as a service) framework for writing portable .NET functions
Git Town - Additional Git commands for easier branch management and support for stacked changes
manual-approval - Pause your GitHub Actions workflow and request manual approval from set approvers before continuing