@cairnvibe/indexer
Cairn's analyzer and installer (the `cairn` CLI) — scans Next.js source or crawls any running app, and scaffolds the backend either way.
This report shows the evidence for @cairnvibe/indexer@0.2.10. 1 of 17 known versions is blocked or flagged. The newest version, 0.5.3, is flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s setup wizard installs an automatic prebuild hook that reuses the configured LLM key on later builds, causing recurring external API calls and potential charges without a distinct opt-in. The provider choice and key prompt make the initial use expected, but do not establish consent to recurring paid calls on routine builds.
Decision evidence
public snapshot- The CLI runs the setup wizard only when the user invokes `cairn setup`.
- Setup appends a `prebuild` script that runs `cairn build` on future project builds, without a separate opt-in for recurring provider calls.
- The wizard accepts an Anthropic or Groq key and uses it for manifest builds; the LLM client sends page source to the selected provider.
- The build writes the generated manifest to the project’s `ui-manifest.json`.
- The setup wizard asks the user to choose Anthropic, Groq, or skip, and prompts for a key.
- Manifest generation and provider calls are part of the package’s analyzer purpose.
- Setup’s usage text describes automatic manifest rebuilding on future builds.
Source & flagged code
6 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/setup.jsView on unpkgFindings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.2.10.
The versions list below shows the verdict for each recorded version.
- Avoid installing @cairnvibe/indexer@0.2.10. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.