@mastra/deployer@1.64.0
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe proxy’s default recipient is package-aligned and use is runtime-triggered, but its configurable upstream is unrestricted while the platform token is forwarded. This warrants a warning for conditional credential exposure, not a block.
Decision evidence
public snapshot- The manifest exposes the server bundle and declares build scripts, with no install lifecycle hook.
- The server proxy requires platform credentials and accepts an environment-configured endpoint with a Mastra service default.
- The proxy sends the platform access token as a bearer credential to the selected upstream endpoint.
- The server proxy is limited to loopback requests and rejects cross-origin requests.
- The endpoint override requires runtime configuration, and the proxy requires both platform credentials; the default endpoint is Mastra’s service.
- The package’s npm install command is inside an explicit lockfile-generation method that runs against its output directory.
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.64.0.
See all versions of @mastra/deployer for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer@1.64.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.