@mastra/deployer@1.62.0
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source shows a real but constrained credential-forwarding risk when an operator overrides the proxy endpoint. The development and loopback gates reduce exposure, while the endpoint override remains unrestricted; this supports a warning rather than a block.
Decision evidence
public snapshot- The package manifest defines no install or other lifecycle hook.
- The development proxy requires platform token and project ID environment variables, and accepts a configurable upstream endpoint.
- The proxy sends the platform token as a bearer credential to the resolved upstream URL.
- The proxy is mounted only when both development mode and Studio are enabled, and it rejects non-loopback requests.
- The proxy defaults to Mastra’s platform endpoint and has development-only, loopback, and same-origin request checks.
Source & flagged code
6 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.62.0.
See all versions of @mastra/deployer for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer@1.62.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.