@pipedream/daytona
Pipedream Daytona Components
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Pipedream org routinely rotates maintainers across its many integration packages; not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same rationale — Pipedream org maintainer rotation is expected and benign. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @daytonaio/sdk is the official Daytona SDK; adding it to a Daytona integration component is expected. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects adding SDK-backed component logic from a near-empty stub; not a payload injection. | ai |
v0.3.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.