| FMRS | 34 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 3 / 20 | 12 / 20 |
|---|
| Security and permissions | 6 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 18 / 20 |
|---|
| Documentation | 8 / 20 | 18 / 20 |
|---|
| Setup experience | 4 / 20 | 15 / 20 |
|---|
| Best for | - AI architects needing persistent memory and cross-model coordination
- Engineers building enterprise multi-window applications, trading platforms, or IDE-class tools
- Researchers studying self-evolving systems, gated recursive self-improvement, and multi-agent governance
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Static content sites or simple blogs
- Teams seeking a drop-in syntax replacement
- Developers unwilling to adopt the Worker Actor Model or treat AI as a peer maintainer
| - 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 | - Access to source code, documentation, issues, pull requests, and discussions for knowledge-base construction
- Persistent storage for agent memory, messages, and graph data
- If GitHub Workflow is enabled, management of issues, pull requests, reviews, labels, and projects
- If Neural Link is enabled, inspection of live application state and mutation of the running application
- Sandboxed file access may be used by internal Neo.ai.Agent local loops
| - 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 | - Neural Link can modify live application state and hot-patch code, so incorrect operations may affect running applications
- GitHub workflows may create or review pull requests, manage issues, and synchronize repository state
- Persistent memory and knowledge stores may retain repository content, discussions, and agent reasoning
- Multi-tenant deployments must preserve tenant identity and visibility isolation; the README gives no specific security configuration
| - 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 Desktop, VS Code, Cursor |
|---|
| Tools | 0 | 19 |
|---|