registry / @cairnvibe/indexer / 0.2.3
@cairnvibe/indexer@0.2.3
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 performs broad but explicit CLI-driven project mutation and source-to-LLM processing. Because it lacks automatic lifecycle execution and the observed behavior is package-aligned, it warrants a warning rather than a publish block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs `cairn setup [dir]`.
Impact
It can change the target project's dependencies, `.env`, UI integration files, and `package.json` prebuild behavior; LLM builds can transmit scanned source to the chosen provider.
Mechanism
Explicit CLI-driven project scaffolding, dependency installation, and build-hook configuration.
AI rationale
The package performs broad but explicit CLI-driven project mutation and source-to-LLM processing. Because it lacks automatic lifecycle execution and the observed behavior is package-aligned, it warrants a warning rather than a publish block.
Evidence
dist/cli.jsdist/setup.jsdist/l3-describe.jsdist/llm.js.envpackage.jsonui-manifest.json
Decision evidence
public snapshotAI called this Suspicious at 85.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The explicit `cairn setup` command installs packages into the selected project, including this package name.
- That setup command writes a `.env` file from keys entered by the user and modifies the target project's build script.
- The CLI can scan application source and send up to 12,000 characters of each page source to a configured Anthropic or Groq client.
Evidence against
- package.json has no preinstall, install, postinstall, or other lifecycle hook.
- The project-changing behavior is reached only through the explicit `cairn setup` CLI command.
- The observed network use is tied to user-configured LLM providers; no hidden endpoint or credential exfiltration path was found.
- The child-process use in manifest generation runs a fixed git command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystem
HighEntropyStrings
Source & flagged code
6 flaggeddist/manifest.jsView file
3exports.assembleManifest = assembleManifest;
L4: const node_child_process_1 = require("node:child_process");
L5: function assembleManifest(rootDir, facts, l2, l3) {
High
dist/l3-describe.jsView file
8exports.describeAll = describeAll;
L9: const node_fs_1 = __importDefault(require("node:fs"));
L10: const node_path_1 = __importDefault(require("node:path"));
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/l3-describe.jsView on unpkg · L8dist/setup.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @cairnvibe/indexer@0.2.0
matchedIdentity = npm:QGNhaXJudmliZS9pbmRleGVy:0.2.0
similarity = 0.684
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical2 High5 Medium3 Low
CriticalPrevious Version Dangerous Deltadist/setup.js
HighChild Processdist/manifest.js
HighRuntime Package Installdist/setup.js
MediumDynamic Requiredist/l3-describe.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencedist/setup.js
MediumAi Review Evidencedist/setup.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.2.3.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.2.3 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.