@anthropic-ai/foundry-sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Anthropic migrated to GitHub Actions CI publishing with SLSA attestation; expected for this official SDK. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is an Anthropic employee (dylanc-anthropic); consistent with org-level SDK maintenance. | ai | |
| source-diff | large-new-source-files | AI (source-diff): SDK expansion; no obfuscation or suspicious patterns flagged alongside the new files. | ai |
v0.2.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. 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.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.