@mastra/daytona@0.11.3
Daytona cloud sandbox provider for Mastra workspaces
AI Security Review
scanned 2d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook in the package manifest and no attack behavior in the required SDK entry files. The weak-crypto hint refers to MD5-based temporary filename derivation, not security-sensitive cryptography.
Decision evidence
public snapshot- The manifest exposes the built runtime and declares @daytonaio/sdk as its runtime dependency; it defines no install lifecycle hook.
- The required SDK manifest has only a documentation script, and its CommonJS and ESM entrypoints export the Daytona SDK API.
- The weak-crypto matches hash mount paths to form temporary credential or mount configuration filenames; they do not use MD5 for security decisions.
Source & flagged code
8 flagged · loading sourceThe weak-crypto matches hash mount paths to form temporary credential or mount configuration filenames; they do not use MD5 for security decisions.
dist/index.jsView on unpkg · L264Findings
Affected versions and remediation
This report applies to @mastra/daytona@0.11.3.
See all versions of @mastra/daytona for other recorded verdicts.
- Review the evidence and your use of @mastra/daytona@0.11.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.