Migrating to Cloudsmith lets an enterprise financial services firm block malicious and non-compliant npm packages at ingestion

A completed migration for an enterprise financial services organization from Mixed or self-managed tooling.

Company size
Enterprise
Industry
Financial Services
Package formats
Developers
201–500
Switching from
Mixed or self-managed tooling

Technology stack

  • GitHub Actions
  • Jenkins
  • Azure DevOps
  • Identity and access management

Before state

Developers and CI pulled npm dependencies directly from the public registry, with security scanning running downstream at pull request time rather than at ingestion. Grown through acquisition, the organization operates four business units across separate technology stacks, three identity providers and two CI stacks, with no central platform team. A series of self-propagating npm supply chain attacks forced a reassessment of that approach, since chasing affected packages after they had already been pulled would not scale.

Pain points and value drivers

  • Developers and CI pulled npm dependencies directly from the public registry, with security scanning running downstream at pull request time rather than at ingestion.
  • Four business units operated on separate technology stacks, across three identity providers and two CI stacks, with no central platform team.
  • A series of self-propagating npm supply chain attacks exposed the limits of scanning packages only after they had already been pulled.
  • No single controlled entry point existed for npm dependencies across business units.

Outcomes

  • Every npm dependency now enters through one controlled point, one repository per business unit.
  • Malicious packages are quarantined and AGPL-licensed packages are blocked at ingestion.
  • Cache-only mode ensures nothing reaches a developer or pipeline that has not been scanned and evaluated first.
Customers

More success stories

Carta

Carta consolidated software assets into a single, cloud-native repository, giving engineers across seven global offices seamless access to packages across multiple formats and technologies.

Thrivent

Thrivent consolidated fragmented tooling into a fully managed artifact platform, eliminating infrastructure bottlenecks and enabling reliable, high-concurrency CI/CD workflows across more than 900 developers.

Seven formats, one control plane

A crypto company replaced a mix of cloud and public registries with one managed platform. It now blocks public registry access per format and can respond quickly to supply chain incidents.

  • AWS CodeArtifact migration
  • GitHub Packages migration