StepSecurity
StepSecurity pitches broader package protection than GitHub firewall
GitHub has rolled out a package firewall in public preview, designed to check npm packages against an enterprise policy before installation. The feature, which applies to GitHub Enterprise Cloud customers, is praised for addressing supply chain risk at the point of installation. By contrast, StepSecurity argues that its Secure Registry plugs a broader gap: it sits between developer machines, CI runners, and public registries and checks every package request against an organisation’s policy.
The article positions Secure Registry as supporting eight ecosystems—npm, PyPI, Maven, NuGet, Go, RubyGems, and Cargo, with Packagist (PHP) in beta—and notes that attacks have affected multiple ecosystems, citing a March 2026 incident involving litellm on PyPI that extracted credentials as soon as it was installed.
The piece highlights several practical capabilities and evidence. Secure Registry logs every request and, with source attribution, links each action to the GitHub Actions run or developer machine responsible for pulling a package, and it maintains an Inventory that lists all packages requested, including their licenses and known vulnerabilities. It asserts that malicious versions are blocked within an hour via Compromised Packages, backed by StepSecurity’s threat intelligence team and SOC.
The article also describes a cooldown mechanism that temporarily holds back new versions yet dynamically resolves to the latest permissible version to keep builds progressing. It explains that Secure Registry enforces policy across both developer machines and CI runners, detailing how Dev Machine Guard and Harden-Runner policies ensure that public registries are not used, thereby preventing bypass of protection.