@mastra/deployer-cloud@1.79.0
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe package has no install hook, and inspected runtime behavior is consistent with cloud deployment, configured logging, and status reporting. No concrete malicious behavior was identified.
Decision evidence
public snapshot- The manifest has no install lifecycle hook; its scripts are for building, testing, and linting.
- The runtime sends build status and runner logs only to environment-configured services, with both sends disabled in CI; storage likewise uses configured credentials and a configured URL.
- The deployer bundles a user project, optionally copies studio assets, and installs dependencies through its deployer method.
- The inspected execa source and its required modules handle subprocess and stream input, output, and transforms; no unrelated collection or transfer is shown in these paths.
- The inspected fs-extra and Redis modules are used for file copying, package metadata reading, and configured logging.
Source & flagged code
5 flaggedPackage contains source files above the normal full-analysis size ceiling.
dist/studio/assets/main-CPed5rup.jsView on unpkgThe manifest has no install lifecycle hook; its scripts are for building, testing, and linting.
package.jsonView on unpkg · L2Findings
Affected versions and remediation
This report applies to @mastra/deployer-cloud@1.79.0.
See all versions of @mastra/deployer-cloud for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer-cloud@1.79.0 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.