---
title: "Artifact management with malware blocking built in"
description: "Three separate artifact tools became one managed platform, and malware is now blocked upstream instead of after an incident. A pilot group led the 10-month rollout across 500+ developers."
canonical_url: "https://cloudsmith.com/customers/migrating-to-cloudsmith-lets-an-enterprise-health-tech-company-centralize-artifact-management"
last_updated: "2026-11-12T10:48:52Z"
---
# Artifact management with malware blocking built in

A completed migration for an enterprise healthcare & life sciences organization from GitHub Packages, AWS CodeArtifact, Cloud container registries and Mixed or self-managed tooling.

## At a glance

- **Company size:** Enterprise
- **Industry:** Healthcare & Life Sciences
- **Package formats:** Cargo, Dart, Docker, Go, Helm, Maven, npm, Python, Raw and Generic Artifacts
- **Developers:** 501–2,000
- **Switching from:** GitHub Packages, AWS CodeArtifact, Cloud container registries, Mixed or self-managed tooling

## Technology stack

- GitHub Actions
- CircleCI
- Security tooling
- Identity and access management

## Before state

The organization managed artifacts across three separate tools: GitHub Packages, AWS CodeArtifact and Amazon ECR, which limited central control and visibility. Malware was only blocked reactively, after an incident, rather than upstream. Manual security rule updates and ad-hoc controls added operational overhead, and onboarding new developers was inconsistent.

## Pain points and value drivers

- Artifacts were spread across three separate tools: GitHub Packages, AWS CodeArtifact and Amazon ECR, limiting central control and visibility.
- Malware was blocked only after an incident, not early in builds.
- Manual security rule updates and ad-hoc controls added operational overhead.
- Onboarding new developers was inconsistent.

## Outcomes

- Centralized artifact management for key publishers behind a single URL.
- Malware blocking and Cargo cooldown moved security upstream, rather than reacting after an incident.
- SAML SSO is enforced and pipelines use dynamic OIDC, removing long-lived secrets from CI.
- A pilot group completed rollout before wider adoption across the organization.
- An AI migration skill was used to update pipelines.
- Developers self-enrolled for entitlement tokens through IdP login.
