Migrating to Cloudsmith lets an SMB security company mitigate zero-day npm supply chain attacks
A completed migration for an SMB technology & software organization from GitHub Packages, Cloud container registries and Mixed or self-managed tooling.
- Company size
- SMB
- Industry
- Technology & Software
- Package formats
- Switching from
- GitHub Packages, Cloud container registries, Mixed or self-managed tooling
Technology stack
- GitHub Actions
- CircleCI
Before state
The customer operated a fragmented package distribution setup split across GitHub Packages and Google Cloud Platform (GCP) Container Registry. Developers pulled dependencies directly from public registries without a central control plane. They lacked perimeter guardrails like malware blocking or cooldown policies, relying instead on post-ingest warnings from GitHub Advanced Security and Dependabot to fill the gaps. The unmitigated exposure to supply chain threats, particularly malicious npm packages, presented a critical brand and operational risk.
Pain points and value drivers
- Package management was scattered across GitHub Packages and GCP Container Registry without unified oversight.
- Directly ingesting third-party dependencies from public registries exposed development pipelines to zero-day and malicious npm attacks.
- The organization depended on reactive tools, such as Dependabot and GitHub Advanced Security warnings, rather than stopping malicious packages at the perimeter.
- The organization lacked capabilities such as automated malware blocking, package quarantine, and time-delay or soak policies.
Outcomes
- The customer consolidated dependency management into a single gateway for all open-source packages across the organization.
- The customer implemented automated malware blocking, package quarantine, and a cooldown policy through enterprise policy management, to address zero-day npm supply chain attacks.
- The customer integrated OIDC and GitHub Actions for keyless authentication and simplified pipeline governance.