@zerodev/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in fallback client proxy to iterate callable methods — standard pattern, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped SDK with 255 versions; missing repo/homepage in package.json is a metadata gap, not a spam signal. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 5.5.10 | 1 / 0 | |
| 5.5.9 | 1 / 0 | |
| 5.5.8 | 1 / 0 | |
| 5.5.5 | 1 / 0 | |
| 5.5.4 | 1 / 0 | |
| 5.5.3 | 1 / 0 | |
| 5.5.2 | 1 / 0 | |
| 5.5.1 | 1 / 0 | |
| 5.5.0 | 1 / 0 | |
| 5.4.42 | 1 / 0 | |
| 5.4.41 | 1 / 0 | |
| 5.4.40 | 1 / 0 | |
| 5.4.39 | 1 / 0 | |
| 5.4.38 | 1 / 0 | |
| 5.4.37 | 1 / 0 | |
| 5.4.36 | 1 / 0 | |
| 5.4.35 | 1 / 0 | |
| 5.4.34 | 1 / 0 | |
| 5.4.33 | 1 / 0 | |
| 5.4.32 | 1 / 0 | |
| 5.4.31 | 1 / 0 |
v5.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.