@mastra/deployer@1.63.1
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The scanner’s process and network findings map to caller-driven validation, deployment output generation, and a loopback-only development proxy to the package’s Mastra service.
Decision evidence
public snapshot- package.json exposes the deployer entry points and lists build, documentation, test, and lint scripts; no install lifecycle script is declared.
- The utility module contains path normalization helpers, with no suspicious behavior in the inspected excerpt.
- The analyzer subprocess is used to import and validate a caller-supplied file; its CommonJS and ESM builds show the same behavior.
- The bundler installs dependencies into deployment output and generates a lockfile there during bundling.
- The Agent Learning proxy is registered only for development with Studio enabled, rejects non-loopback and cross-origin requests, and sends the platform token to the Mastra endpoint.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/utils-O98BGdnP.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @mastra/deployer@1.63.1.
See all versions of @mastra/deployer for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer@1.63.1 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.