| FMRS | 43 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 4 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 8 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 |
|---|
| Best for | - Developers who regularly use Claude Code, Codex CLI, Gemini CLI, or other supported AI coding CLIs.
- Users seeking to reduce context usage from large repositories, logs, screenshots, and skill files.
- Users comfortable with modifying local AI-client configuration and creating indexes and caches.
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users seeking a standard MCP server manifest, documented MCP transport, or directly callable MCP tool inventory.
- Users who do not want a global npm package, registered hooks, or client-configuration changes.
- Production users requiring validated macOS support; the README labels macOS as untested.
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Requires installing a global Node.js/npm package.
- Requires writing client configuration and hook files for supported AI tools.
- Requires reading project files, Git information, and relevant session data to build indexes, caches, and compact manifests.
- The optional worker runs as a local background process.
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Hooks intercept or rewrite reads, Bash commands, screenshots, and other tool calls, which can change how original output is presented.
- Indexes, caches, and session manifests store project or tool output locally; the README does not document complete retention or encryption behavior.
- The README claims to scan fetched web content and block prompt injection, but this should not replace human review or the client's own security controls.
- Some bridges are not validated against live instances, including the documented Qwen, OpenClaw, and pi integrations; Copilot hook failures can deny all tool calls in a session.
- Repository metadata says NOASSERTION for the license, while the README badge shows PolyForm Noncommercial; verify the repository license before use.
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Code, Codex, Gemini CLI, Qwen Code, GitHub Copilot CLI, OpenCode, pi, Grok CLI | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 0 | 19 |
|---|