mint@4.2.1135
The Mintlify CLI
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe package manifest has no install lifecycle hook and exposes a CLI wrapper that forwards user arguments to its pinned first-party CLI dependency. The inspected entrypoint source shows no attack behavior.
Decision evidence
public snapshot- package.json exposes index.js as the CLI and depends on the fixed @mintlify/cli release; its scripts contain only clean:all.
- The inspected CLI package manifest maps its command to bin/index.js.
- bin/index.js forwards caller-supplied arguments to the CLI start entrypoint, and index.js imports that first-party CLI; no attack behavior was identified in these paths.
Source & flagged code
4 flaggedpackage.json exposes index.js as the CLI and depends on the fixed @mintlify/cli release; its scripts contain only clean:all.
package.jsonView on unpkg · L28The inspected CLI package manifest maps its command to bin/index.js.
.lpm-dependency-evidence-e4ddf257-07ff-41af-a0e5-e3e09dec967c/0/npm-linux/package.jsonView on unpkg · L28Findings
Affected versions and remediation
This report applies to mint@4.2.1135.
See all versions of mint for other recorded verdicts.
- Review the evidence and your use of mint@4.2.1135 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.