@mastra/deployer@1.73.0
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged process execution is used for project build validation or constrained service commands. The inspected source does not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes the deployer entrypoints and contains no install lifecycle hook; its scripts are build, spec-fetch, test, and lint commands.
- The services helper rejects shell arguments outside a restrictive character set before spawning a process.
- The analyzer starts Node to import a project file during validation, and its caller validates generated entry files.
- The CommonJS analyzer contains the same validation flow; these findings are consistent with a build and deployment tool.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
dist/services-D-iHFbpf.jsView on unpkg · L6Package source references dynamic require/import behavior.
Findings
Affected versions and remediation
This report applies to @mastra/deployer@1.73.0.
See all versions of @mastra/deployer for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer@1.73.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.