registry / @mastra/deployer / 1.66.0
@mastra/deployer@1.66.0
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo concrete malicious install-time behavior, exfiltration path, or self-dependency chain was found. Because the compiled package contains user-code execution and package-manager invocation and the supplied analysis coverage is incomplete, this is a warning rather than a clean mark.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A consumer explicitly invokes bundling, deployment, or validation APIs.
Impact
A deployment workflow can run its own project code and modify its generated output, so it warrants caution but does not establish malicious behavior.
Mechanism
Subprocess validation and output-directory dependency installation.
AI rationale
No concrete malicious install-time behavior, exfiltration path, or self-dependency chain was found. Because the compiled package contains user-code execution and package-manager invocation and the supplied analysis coverage is incomplete, this is a warning rather than a clean mark.
Evidence
dist/bundler/index.jsdist/analyze-Dv1x8tVU.jsdist/analyze-BLWZxG59.cjsdist/server/index.cjsnode_modulesnode_modules.__tmppackage-lock.json
Network endpoints1
output.signals.mastra.ai
Decision evidence
public snapshotAI called this Suspicious at 72.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The bundler runs npm with force while generating a deployment lockfile.
- The analyzer starts a Node subprocess that imports a caller-selected local file.
- The server can forward a configured platform token to a Mastra endpoint, but only from a loopback request.
- Compiled utilities load the child-process module.
Evidence against
- The manifest has no preinstall, install, or postinstall hook.
- Process execution is inside bundling and validation methods, not package import-time code.
- The npm command is limited to a supplied output directory and is described as lockfile generation.
- The token-bearing request requires both configured environment variables and loopback-origin checks.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcedist/utils-O98BGdnP.cjsView file
1require("child_process");
L2: require("fs");
High
Child Process
Package source references child process execution.
dist/utils-O98BGdnP.cjsView on unpkg · L1dist/analyze-Dv1x8tVU.jsView file
342"#tools",
L343: "execa",
L344: "effect",
High
dist/validator/custom-resolver.cjsView file
1Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
L2: const require_utils = require("../utils-O98BGdnP.cjs");
L3: let fs = require("fs");
Findings
1 Critical5 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/bundler-DQ1CSoFJ.cjs
HighChild Processdist/utils-O98BGdnP.cjs
HighShelldist/analyze-Dv1x8tVU.js
HighCross File Remote Execution Contextdist/analyze-BLWZxG59.cjs
HighRuntime Package Installdist/bundler/index.js
HighSemantic Analysis Limitedpackage.json
MediumDynamic Requiredist/validator/custom-resolver.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @mastra/deployer@1.66.0.
See all versions of @mastra/deployer for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer@1.66.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.