Adopting Cloudsmith lets an SMB health research organization standardize artifact management and strengthen security posture
A completed adoption for an SMB healthcare & life sciences organization.
- Company size
- SMB
- Industry
- Healthcare & Life Sciences
- Package formats
- Developers
- 51–200
- Switching from
- Azure Artifacts, GitHub Packages, Mixed or self-managed tooling
Technology stack
- GitHub Actions
Before state
External dependencies were pulled directly from public registries with no central control, and internal artifacts were scattered across multiple platforms, including Azure and GitHub, with no single source of truth. As the custodian of sensitive health and genetic data, that gap sat at odds with the public trust the organization depends on.
Pain points and value drivers
- External dependencies were pulled directly from public registries with no central control.
- Internal artifacts were scattered across multiple platforms, including Azure and GitHub, with no single source of truth.
Outcomes
- Artifact management is now consolidated and standardized in one place, with baseline policies for vulnerabilities and license compliance applied across the organization.
- A stronger security posture has been established.