create-mastra@1.32.1
Create Mastra apps with one command
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe configurable authentication destination creates conditional credential exposure, while explicit agent skill installation adds a guarded agent capability. Neither behavior establishes malicious intent or qualifies for publication blocking.
Decision evidence
public snapshot- The platform API destination accepts an unrestricted MASTRA_PLATFORM_API_URL override.
- Authentication loads saved Mastra credentials and sends the access token for verification and the refresh token for renewal to that destination.
- The active create command invokes authentication after the user accepts observability setup; this consent does not restrict the credential recipient.
- Project setup installs Mastra skills for detected coding agents through npx with automatic confirmation; --no-skills disables this behavior.
- The flagged MCP configuration location only constructs paths and performs no configuration write.
- package.json has no automatic installation lifecycle hooks or runtime self-dependency.
- The default authentication destination is Mastra's platform, and observability requires an interactive choice.
- No covert recipient, destructive behavior, or malicious intent was established.
Source & flagged code
8 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/index.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to create-mastra@1.32.1.
See all versions of create-mastra for other recorded verdicts.
- Review the evidence and your use of create-mastra@1.32.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.