registry / @cairnvibe/indexer / 0.4.4
@cairnvibe/indexer@0.4.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 3d ago · by lpm-firewall-aiThe flagged package installation and project edits are part of the advertised setup and update workflows and require explicit CLI use. No malicious credential flow, unrelated collection, or automatic install-time behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI commands explicitly selected by the user; importing the main entry only exposes library functions.
Impact
Expected project setup and update changes. No automatic credential collection or unrelated data transfer was identified.
Mechanism
Setup scaffolds files, installs Cairn dependencies, and configures future manifest builds; update checks package versions and prompts before installing by default.
AI rationale
The flagged package installation and project edits are part of the advertised setup and update workflows and require explicit CLI use. No malicious credential flow, unrelated collection, or automatic install-time behavior was identified.
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI; its main entry point only re-exports library functions, and the manifest declares no lifecycle scripts.
- The flagged npm install runs only from the explicit `cairn setup` command and installs Cairn packages into the chosen project.
- Setup asks the user to choose an LLM provider and enter a key, with an option to skip; the CLI’s build command uses the selected provider client.
- Setup adds a prebuild script to regenerate the manifest as part of future project builds.
- `cairn update` asks before installing updates unless the user explicitly passes `--apply` or `--yes`.
Evidence against
- Setup and update invoke npm and modify project files, but these actions are reached through explicit CLI commands.
- The new Google GenAI dependency declares a no-op `preinstall` script.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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/update.js
HighSemantic Analysis Limiteddist/cli.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.4.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.4.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.