@cairnvibe/indexer@0.4.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 3d ago · by lpm-firewall-aiThe flagged process execution is confined to explicit setup, update, and removal commands. Setup’s project analysis sends source to the LLM provider the user selects, consistent with the package’s analyzer purpose; no unrelated credential flow or concealed install-time behavior was found.
Decision evidence
public snapshot- The manifest exposes a CLI and library entry point, with only build and typecheck scripts and no install lifecycle script.
- The CLI invokes setup, update, and remove only for their corresponding explicit commands.
- Setup installs a fixed list of Cairn packages when the user runs the setup wizard.
- Setup asks the user to choose an LLM provider and enter that provider’s key; the initial build runs only when a key was supplied.
- The analyzer sends project page source and element data to the selected LLM client to generate descriptions, matching the package’s stated purpose.
- Setup adds a prebuild command to regenerate the manifest on future builds.
- No credential collection or unrelated network transmission was identified.
- Update asks for confirmation before installing unless the user explicitly passes an apply/yes flag.
- The library entry point exports analysis functions without invoking the CLI.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
dist/remove.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.4.3.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.4.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.