@mastra/deployer@1.77.0
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed subprocess and configuration writes are scoped to deployment or caller-supplied validation. Static hints about shell use and network-capable build code do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines build, watch, API-spec, test, and lint scripts; it defines no preinstall, install, or postinstall hook.
- The manifest declares @mastra/server as a dependency, not a runtime dependency on @mastra/deployer itself.
- The deploy helper filters copied pnpm workspace settings through a fixed key set and validates build-approval entries.
- The helper reads workspace configuration and writes a pnpm workspace file into the supplied deployment directory.
- Package installation is launched by the deployment helper with that directory as its working root.
- The analyzer's subprocess wrapper runs a supplied command and handles its result as a validation process.
- The CommonJS analyzer's validate function constructs a Node process to import and validate a supplied file.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
dist/services-DXqmEy8F.jsView on unpkg · L6Package source references dynamic require/import behavior.
Findings
Affected versions and remediation
This report applies to @mastra/deployer@1.77.0.
See all versions of @mastra/deployer for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer@1.77.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.