@anthropic-ai/vertex-sdk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers follow Anthropic's internal naming convention (*-anthropic); consistent with org-internal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of boris-anthropic alongside addition of other Anthropic-namespaced accounts indicates routine team rotation, not takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): High-traffic official Anthropic SDK; dormancy likely reflects SDK consolidation cadence, not account compromise. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 2 / 0 | |
| 0.15.0 | 2 / 0 | |
| 0.14.4 | 2 / 0 | |
| 0.14.3 | 2 / 0 | |
| 0.14.2 | 2 / 0 | |
| 0.14.0 | 2 / 0 | |
| 0.13.2 | 2 / 0 | |
| 0.13.1 | 2 / 0 | |
| 0.13.0 | 2 / 0 | |
| 0.12.1 | 2 / 0 | |
| 0.12.0 | 2 / 0 | |
| 0.11.5 | 2 / 0 | |
| 0.11.4 | 2 / 0 | |
| 0.11.3 | 2 / 0 | |
| 0.11.2 | 2 / 0 | |
| 0.11.1 | 2 / 0 | |
| 0.11.0 | 2 / 0 |
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.