@cairnvibe/indexer@0.2.8
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 package has no install hook, and importing its library entry only exposes API functions. Dependency installation and project edits happen through the user-invoked setup wizard, while generated WebMCP actions are limited to statically traced same-origin requests.
Decision evidence
public snapshot- The manifest declares no install, preinstall or postinstall hook; its scripts are build and typecheck.
- The library entry point exports functions and classes without starting the CLI at import time.
- The package installer runs only inside the explicit `cairn setup` command and installs the package’s documented Cairn dependencies.
- Setup asks the user whether to configure an LLM provider and prompts for its key; the key is then used to build the manifest.
- Manifest action parsing accepts only static, same-origin relative URLs and mutating HTTP methods.
- The CLI has a `setup` command that can install dependencies, write project files and add a prebuild script.
- The generated WebMCP component can register traced mutating actions for browser agents when a user generates and adds it to their app.
Source & flagged code
6 flaggedPackage source invokes a package manager install command at runtime.
dist/setup.jsView on unpkg · L170Findings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.2.8.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Review the evidence and your use of @cairnvibe/indexer@0.2.8 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.