mint@4.2.1134
The Mintlify CLI
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest contains no install lifecycle hook, and the inspected launcher runs the CLI only when invoked. These source facts support a clean verdict.
Decision evidence
public snapshot- The package manifest exposes a CLI and declares no install lifecycle hook; its only script removes its own node_modules directory.
- The declared CLI dependency exposes bin/index.js, which starts the CLI when invoked and passes user arguments to the child process without enabling a shell.
Source & flagged code
3 flaggedThe package manifest exposes a CLI and declares no install lifecycle hook; its only script removes its own node_modules directory.
package.jsonView on unpkg · L28The declared CLI dependency exposes bin/index.js, which starts the CLI when invoked and passes user arguments to the child process without enabling a shell.
.lpm-dependency-evidence-d8b3bddd-afc9-48c1-a31c-e0b459645c65/0/npm-linux/package.jsonView on unpkg · L28Findings
Affected versions and remediation
This report applies to mint@4.2.1134.
See all versions of mint for other recorded verdicts.
- Review the evidence and your use of mint@4.2.1134 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.