@mastra/deployer-sandbox@0.3.23
Deploy a Mastra server into any workspace sandbox that supports networking and get a live public URL
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no install hook or confirmed attack behavior. Runtime file, command, and network operations support the package's sandbox deployment function and are invoked through its deployment API or optional alias configuration.
Decision evidence
public snapshot- package.json has no install lifecycle hook and declares fs-extra and @mastra/deployer as runtime dependencies.
- The inspected dependency manifests show no install lifecycle hooks; fs-extra's ESM entry exports file utilities, and @mastra/deployer's entry exposes deployer and build services.
- The package's deploy method passes loaded environment variables into the sandbox deployment and records deployment metadata.
- The shared runtime code runs commands inside the sandbox; its default deployment directory is under the sandbox home.
- The Vercel Edge Config request requires a caller-provided token and is performed only when alias configuration is present.
Source & flagged code
5 flaggedPackage contains source files above the normal full-analysis size ceiling.
dist/studio/assets/main-CPed5rup.jsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.cjs#virtual:normalized:round1View on unpkgFindings
Affected versions and remediation
This report applies to @mastra/deployer-sandbox@0.3.23.
See all versions of @mastra/deployer-sandbox for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer-sandbox@0.3.23 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.