@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, so a manually published version cannot be tied back to a reviewed commit.
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 100 of 128)
| 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 | |
| 5.4.30 | 1 / 0 | |
| 5.4.29 | 1 / 0 | |
| 5.4.28 | 1 / 0 | |
| 5.4.27 | 1 / 0 | |
| 5.4.26 | 1 / 0 | |
| 5.4.25 | 1 / 0 | |
| 5.4.24 | 1 / 0 | |
| 5.4.23 | 1 / 0 | |
| 5.4.22 | 1 / 0 | |
| 5.4.21 | 1 / 0 | |
| 5.4.20 | 1 / 0 | |
| 5.4.19 | 1 / 0 | |
| 5.4.18 | 1 / 0 | |
| 5.4.17 | 1 / 0 | |
| 5.4.16 | 1 / 0 | |
| 5.4.15 | 1 / 0 | |
| 5.4.14 | 1 / 0 | |
| 5.4.13 | 1 / 0 | |
| 5.4.12 | 1 / 0 | |
| 5.4.11 | 1 / 0 | |
| 5.4.10 | 1 / 0 | |
| 5.4.9 | 1 / 0 | |
| 5.4.8 | 1 / 0 | |
| 5.4.7 | 1 / 0 | |
| 5.4.6 | 1 / 0 | |
| 5.4.5 | 1 / 0 | |
| 5.4.4 | 1 / 0 | |
| 5.4.3 | 1 / 0 | |
| 5.4.2 | 1 / 0 | |
| 5.4.1 | 1 / 0 | |
| 5.4.0 | 1 / 0 | |
| 5.3.26 | 1 / 0 | |
| 5.3.25 | 1 / 0 | |
| 5.3.24 | 1 / 0 | |
| 5.3.23 | 1 / 0 | |
| 5.3.22 | 1 / 0 | |
| 5.3.21 | 1 / 0 | |
| 5.3.20 | 1 / 0 | |
| 5.3.19 | 1 / 0 | |
| 5.3.18 | 1 / 0 | |
| 5.3.17 | 1 / 0 | |
| 5.3.16 | 1 / 0 | |
| 5.3.15 | 1 / 0 | |
| 5.3.14 | 1 / 0 | |
| 5.3.13 | 1 / 0 | |
| 5.3.12 | 1 / 0 | |
| 5.3.11 | 1 / 0 | |
| 5.3.10 | 1 / 0 | |
| 5.3.9 | 1 / 0 | |
| 5.3.8 | 1 / 0 | |
| 5.3.7 | 1 / 0 | |
| 5.3.6 | 1 / 0 | |
| 5.3.5 | 1 / 0 | |
| 5.3.4 | 1 / 0 | |
| 5.3.3 | 1 / 0 | |
| 5.3.2 | 1 / 0 | |
| 5.3.1 | 1 / 0 | |
| 5.3.0 | 1 / 0 | |
| 5.2.19 | 1 / 0 | |
| 5.2.18 | 1 / 0 | |
| 5.2.17 | 1 / 0 | |
| 5.2.16 | 1 / 0 | |
| 5.2.15 | 1 / 0 | |
| 5.2.14 | 1 / 0 | |
| 5.2.13 | 1 / 0 | |
| 5.2.12 | 1 / 0 | |
| 5.2.11 | 1 / 0 | |
| 5.2.10 | 1 / 0 | |
| 5.2.9 | 1 / 0 | |
| 5.2.8 | 1 / 0 | |
| 5.2.7 | 1 / 0 | |
| 5.2.6 | 1 / 0 | |
| 5.2.5 | 1 / 0 | |
| 5.2.4 | 1 / 0 | |
| 5.2.3 | 1 / 0 | |
| 5.2.2 | 1 / 0 | |
| 5.2.1 | 1 / 0 | |
| 5.2.0 | 1 / 0 | |
| 5.1.18 | 1 / 0 |
v5.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.29
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leekt216) than the most recent previously approved version (justinzen) on 2025-04-23, but leekt216 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.28
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (justinzen) than the most recent previously approved version (sahilvasava) on 2025-03-26, but justinzen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (justinzen) than the most recent previously approved version (sahilvasava) on 2025-03-24, but justinzen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-12-17, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-12-12, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (sahilvasava) on 2024-12-06, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.24
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-10-26, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-10-23, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (sahilvasava) on 2024-10-16, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.21
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (sahilvasava) on 2024-10-16, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.20
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (blakecduncan) on 2024-10-03, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.19
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (blakecduncan) on 2024-10-01, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.18
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blakecduncan) than the most recent previously approved version (sahilvasava) on 2024-09-26, but blakecduncan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (sahilvasava) on 2024-09-25, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-09-17, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-09-14, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-08-28, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-08-22, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (sahilvasava) on 2024-08-19, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (sahilvasava) on 2024-07-16, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.19
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-06-10, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.18
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (blakecduncan) on 2024-06-04, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (blakecduncan) on 2024-05-31, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blakecduncan) than the most recent previously approved version (adnpark) on 2024-05-30, but blakecduncan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-05-23, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adnpark) than the most recent previously approved version (blakecduncan) on 2024-05-16, but adnpark is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (blakecduncan) on 2024-05-14, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.