harden-runner
packj
Our great sponsors
harden-runner | packj | |
---|---|---|
15 | 38 | |
491 | 614 | |
6.1% | 4.9% | |
7.5 | 7.2 | |
7 days ago | 25 days ago | |
TypeScript | Python | |
Apache License 2.0 | 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.
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
packj
-
Rust Without Crates.io
Creator of Packj [1] here. How do you envision sandboxing/security policies will be specified? Per-lib policies when you've hundreds of dependencies will become overwhelming. Having built an eBPF-based sandbox [2], I anticipate that accuracy will be another challenge here: too restrictive will block functionality, too permissive defeats the purpose.
1. https://github.com/ossillate-inc/packj flags malicious/risky NPM/PyPI/RubyGems/Rust/Maven/PHP packages by carrying out static+dynamic+metadata analysis.
-
A Study of Malicious Code in PyPI Ecosystem
Cool project. How do you feel about projects like OpenSSF scorecards or even the checks that socket.dev do today on these packages to help determine risk?
https://github.com/ossillate-inc/packj/blob/main/.packj.yaml
Secondly, what about impersonation where attackers imitate a popular package and its respective metadata?
-
How to use Podman inside of a container
I built Packj [1] sandboxing for securing “pip/NPM install”. It uses strace for sandboxing and blocks access to sensitive files and limits traffic to known-good IP addresses.
1. https://github.com/ossillate-inc/packj
-
NPM Provenance Public Beta
Great work! This provenance check is going to be very valuable for enforcing supply-chain security. We are working on adding support to check for provenance in Packj.
1. https://github.com/ossillate-inc/packj flags risky/malicious NPM/PyPI/Ruby dependencies
-
Show HN: TypeScript Security Scanner
Cool project. Would love to integrate this in Packj [1] as one of the open-source SAST scanners. Will DM you.
1. https://github.com/ossillate-inc/packj flags malicious/risky open-source dependencies.
- Packj flags malicious/risky open-source packages
-
Show HN: Coder Guard – Protect Your IDE from Malicious Extensions
Very cool! I've built something similar, but for packages: https://github.com/ossillate-inc/packj Would love to talk.
-
Ask HN: What Are You Working on This Year?
Working on a marketplace (based on Packj [1]) to allow open-source developers to make money by selling "assured" software artifacts.
1. Packj https://github.com/ossillate-inc/packj flags malicious and other "risky" open-source dependencies in your software supply chain.
-
Compromised PyTorch-nightly dependency chain December 30th, 2022
I’ve created Packj sandbox [1] for “safe installation” of PyPI/NPM/Rubygems packages
1. https://github.com/ossillate-inc/packj
It DOES NOT require a VM/Container; uses strace. It shows you a preview of file system changes that installation will make and can also block arbitrary network communication during installation (uses an allow-list).
-
Vulnerability scanner written in Go that uses osv.dev data
Great to see a developer-friendly tool around OSV! Packj [1] uses OSV APIs to report vulnerable PyPI/NPM/Rubygems packages. Disclaimer: I built it.
1. https://github.com/ossillate-inc/packj flags malicious/risky packages.
What are some alternatives?
repo
kubesploit - Kubesploit is a cross-platform post-exploitation HTTP/2 Command & Control server and agent written in Golang, focused on containerized environments.
actual-malware - Useful library dependency
paperclips - Universal Paperclips mirror
sigstore-website - Codebase for sigstore.dev
meta - Meta discussions and unicorns. Not necessarily in that order.
auth - A GitHub Action for authenticating to Google Cloud.
maloss - Towards Measuring Supply Chain Attacks on Package Managers for Interpreted Languages
scorecard - OpenSSF Scorecard - Security health metrics for Open Source
roqr - QR codes that will rock your world
github-actions-goat - GitHub Actions Goat: Deliberately Vulnerable GitHub Actions CI/CD Environment
firejail - Linux namespaces and seccomp-bpf sandbox