@workos/migrations
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): WorkOS org migrated publishing to GitHub Actions with SLSA provenance; stable pattern for this scoped package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is consistent with WorkOS org team expansion; SLSA attestation confirms CI/CD integrity. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 10 / 15 | |
| 2.2.0 | 10 / 15 | |
| 2.1.3 | 10 / 15 | |
| 2.0.0 | 10 / 15 |
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.