@mastra/deployer@1.78.0
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged execution paths are tied to explicit deployment or validation operations. The subprocess checks and project-file import are consistent with the package's stated role; the inspected source establishes no attack behavior.
Decision evidence
public snapshot- package.json lists build, watch, OpenAPI, test, and lint scripts, with no install lifecycle hook.
- The subprocess wrapper rejects arguments outside a restricted character set before invoking a shell.
- The analyzer's validator runs when given a file and imports that file in a child Node process, consistent with validating a project entrypoint.
- The exported deployer helper receives an entry file and passes it to configuration extraction.
- The package uses shell subprocesses for deployment and dependency-management operations.
- The analyzer imports the supplied project file during validation; these are user-invoked development operations, not install-time package behavior.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
dist/services-DXqmEy8F.jsView on unpkg · L6Package source references dynamic require/import behavior.
Findings
Affected versions and remediation
This report applies to @mastra/deployer@1.78.0.
See all versions of @mastra/deployer for other recorded verdicts.
- Review the evidence and your use of @mastra/deployer@1.78.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.