@cairnvibe/indexer@0.5.1
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 3d ago · by lpm-firewall-aiThe package declares no install lifecycle hook, and importing its library entry point only exposes functions. The flagged installs and project writes are part of the explicit setup workflow, while provider requests analyze project pages using a provider and key selected by the user.
Decision evidence
public snapshot- package.json defines a CLI and library entry point, with no install lifecycle script.
- Importing dist/index.js exposes library functions; command actions are dispatched only when the CLI receives the corresponding command.
- cairn setup prompts the user to choose an LLM provider before requesting its key.
- The build sends page source and UI element data to the selected LLM provider to generate page descriptions.
- Setup writes a root AGENTS.md only when one does not already exist, and its stub points to the generated Cairn reference document.
- cairn setup installs packages, writes project configuration and may build a manifest; these actions are tied to the explicit setup command.
- Manifest generation sends up to 12,000 characters of project source per page to the selected provider, consistent with the analyzer’s stated purpose.
Source & flagged code
6 flaggedPackage source references a known benign dynamic code generation pattern.
dist/clack.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.5.1.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.5.1 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.