@cairnvibe/indexer@0.2.4
Cairn's analyzer and installer (the `cairn` CLI) — scans Next.js source or crawls any running app, and scaffolds the backend either way.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has risky, broad project-mutation and authenticated crawling capabilities behind explicit CLI commands, so it warrants a warning. It is not malicious under the install-hook policy because package installation alone triggers no lifecycle behavior.
Decision evidence
public snapshot- The explicit cairn setup command runs npm install including this package's own name.
- Setup writes user-supplied API keys to a project .env file and modifies package scripts.
- The CLI can crawl a supplied URL with a saved authenticated browser session and send collected page content to an LLM.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Risky setup behavior is reached only through the explicit cairn setup command.
- No source evidence shows secret theft, hidden network destination, obfuscation, or automatic execution on package installation.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/l3-describe.jsView on unpkg · L8Findings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.2.4.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.2.4 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.