@cairnvibe/indexer@0.2.6
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 an explicit-user-command, self-installing project setup path with persistent consumer-project changes and source disclosure to configured LLM providers. It lacks install-time hooks and concrete malicious behavior, so this is a warning rather than a block.
Decision evidence
public snapshot- The explicit setup command can install the package's own name into the consumer project at runtime.
- Setup writes supplied API keys to .env and rewrites consumer package scripts, including prebuild and optionally dev.
- Build sends scanned application source to configured Anthropic or Groq SDK clients.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The setup path is reached only through the explicit cairn setup CLI command.
- No hidden endpoint, secret harvesting, destructive deletion, or automatic execution on import was found.
Source & flagged code
7 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.6.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.2.6 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.