@anthropic-ai/vertex-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Placeholder version under trusted @anthropic-ai scope; real package is legitimate SDK. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a reserved/placeholder version for this official scoped package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual publisher to GitHub Actions CI/CD; SLSA provenance confirms legitimate automation. | ai | |
| 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 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 2 / 0 | |
| 0.18.0 | 2 / 0 | |
| 0.17.1 | 2 / 0 | |
| 0.17.0 | 2 / 0 | |
| 0.16.1 | 2 / 0 | |
| 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 | |
| 0.7.0 | 2 / 0 | |
| 0.6.4 | 2 / 0 | |
| 0.6.1 | 2 / 0 | |
| 0.6.0 | 2 / 0 | |
| 0.5.2 | 2 / 0 | |
| 0.5.1 | 2 / 0 | |
| 0.5.0 | 2 / 0 | |
| 0.4.3 | 2 / 0 | |
| 0.4.2 | 2 / 0 | |
| 0.4.1 | 2 / 0 | |
| 0.4.0 | 2 / 0 | |
| 0.3.7 | 2 / 0 | |
| 0.3.6 | 2 / 0 | |
| 0.3.5 | 2 / 0 | |
| 0.3.4 | 2 / 0 | |
| 0.3.3 | 2 / 0 | |
| 0.3.2 | 2 / 0 | |
| 0.3.1 | 2 / 0 | |
| 0.3.0 | 2 / 0 | |
| 0.2.2 | 2 / 0 | |
| 0.2.1 | 2 / 0 | |
| 0.2.0 | 2 / 0 | |
| 0.1.2 | 2 / 0 | |
| 0.1.0 | 2 / 0 | |
| 0.0.0 | 0 / 0 |
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.