@daytona/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:toplevel-fetch | AI (semgrep): fetch() is used for a documented bulk-upload API call to a configurable basePath; not telemetry or exfiltration. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Require target is a hardcoded relative path string, not user-controlled input; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Daytona SDK is a legitimate package; missing provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@daytona/api-client | AI (dependencies): First-party sibling package from the same org/publisher; versioned in lockstep with this SDK. | ai | |
| dependencies | unvetted-dep:@daytona/toolbox-api-client | AI (dependencies): First-party sibling package from the same org/publisher; versioned in lockstep with this SDK. | ai | |
| dependencies | unvetted-dep:expand-tilde | AI (dependencies): Stable, widely-used utility (~2M weekly downloads); no known advisories. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.184.0 | 23 / 0 | |
| 0.183.0 | 23 / 0 | |
| 0.182.0 | 23 / 0 | |
| 0.180.0 | 23 / 0 | |
| 0.179.0 | 23 / 0 | |
| 0.178.0 | 23 / 0 | |
| 0.175.0 | 23 / 0 | |
| 0.173.0 | 23 / 0 | |
| 0.172.0 | 23 / 0 | |
| 0.171.0 | 23 / 0 | |
| 0.170.0 | 23 / 0 | |
| 0.169.0 | 23 / 0 | |
| 0.168.0 | 23 / 0 | |
| 0.167.0 | 23 / 0 | |
| 0.166.0 | 23 / 0 | |
| 0.165.0 | 23 / 0 | |
| 0.164.0 | 23 / 0 | |
| 0.163.0 | 23 / 0 | |
| 0.162.0 | 23 / 0 |
v0.184.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.183.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.182.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.180.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.179.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.178.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.175.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.173.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.172.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.171.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.170.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.169.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.168.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.167.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.166.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.165.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.164.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.163.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.162.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.