@daytonaio/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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): Babel preset loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:typedoc | AI (phantom-deps): Docs tooling dep loaded via config, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/shell-quote | AI (phantom-deps): Type-only package; stable false positive. | ai | |
| phantom-deps | phantom-dep:typedoc-plugin-markdown | AI (phantom-deps): Docs tooling plugin loaded via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Babel preset loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:typedoc-plugin-merge-modules | AI (phantom-deps): Docs tooling plugin loaded via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/tar | AI (phantom-deps): Type-only package, framework-scoped; stable false positive. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetch call is a documented file upload API endpoint, not telemetry or exfiltration. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Lazy-load pattern for optional modules with a hardcoded relative path; not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared dep likely used indirectly or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@dotenvx/dotenvx | AI (phantom-deps): Declared dep used via config/CLI invocation pattern; stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used to wrap Python sandbox code for matplotlib execution; not a malicious payload pattern. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 0.25.3 | 13 / 0 | |
| 0.25.1 | 12 / 0 | |
| 0.25.0 | 12 / 0 | |
| 0.24.3 | 12 / 0 | |
| 0.24.2 | 11 / 0 | |
| 0.24.0 | 9 / 0 | |
| 0.22.1 | 11 / 0 | |
| 0.22.0 | 20 / 0 | |
| 0.21.9 | 20 / 0 | |
| 0.21.8 | 9 / 0 | |
| 0.21.7 | 20 / 0 | |
| 0.21.2 | 13 / 0 | |
| 0.19.0 | 20 / 0 | |
| 0.18.1 | 5 / 7 | |
| 0.18.0 | 5 / 7 | |
| 0.17.0 | 4 / 7 | |
| 0.16.1 | 4 / 7 | |
| 0.16.0 | 3 / 7 | |
| 0.15.1 | 4 / 7 |
v0.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.