registry / @cairnvibe/indexer / 0.4.0
@cairnvibe/indexer@0.4.0
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 manifest has no install hooks, and importing the package exposes analyzer functions without running setup. The flagged package installation is inside an explicit setup command, which installs named Cairn packages and prompts the user before using an LLM key for project analysis.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
No automatic trigger identified. Setup and removal run through explicit CLI commands; the import entry point only exposes API functions.
Impact
No attack identified. The observed project analysis and LLM requests are consistent with the package’s stated purpose and user-invoked commands.
Mechanism
Setup installs named Cairn packages and prompts for an LLM provider and key; the analyzer sends project source for page descriptions.
AI rationale
The manifest has no install hooks, and importing the package exposes analyzer functions without running setup. The flagged package installation is inside an explicit setup command, which installs named Cairn packages and prompts the user before using an LLM key for project analysis.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to a CLI and an API entry point, with no install lifecycle scripts.
- The import entry point exposes analyzer functions and does not invoke setup.
- The CLI runs setup only when the user selects the `setup` command; setup installs a fixed list of Cairn packages.
- The setup wizard asks the user to choose an LLM provider and enter its API key.
- The LLM client sends project source to describe pages as part of the package’s analyzer purpose.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/remove.jsView file
19const node_path_1 = __importDefault(require("node:path"));
L20: const node_child_process_1 = require("node:child_process");
L21: const install_manifest_1 = require("./install-manifest");
High
17exports.runRemove = runRemove;
L18: const node_fs_1 = __importDefault(require("node:fs"));
L19: const node_path_1 = __importDefault(require("node:path"));
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/remove.jsView on unpkg · L17dist/clack.jsView file
30// situation (used by ts-node, Jest, and others bridging CJS callers to
L31: // ESM-only packages): constructing the import call via `new Function(...)`
L32: // hides it from TypeScript's compiler entirely, so what actually runs at
Low
Eval
Findings
1 Critical3 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/setup.js
HighChild Processdist/remove.js
HighRuntime Package Installdist/setup.js
HighSemantic Analysis Limiteddist/setup.js#virtual:normalized:round1
MediumDynamic Requiredist/remove.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/clack.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.4.0.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.4.0 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.