Name: deps-check
Author: ZenRay

Prompt file imported from ZenRay/CursorTemplate (.cursor/commands/deps-check.md). Copyright stays with the author.

/deps-check — Dependency Check

Analyze project dependencies for updates, security, and best practices.

Check Areas

Security

Known vulnerabilities (via npm audit, safety, etc.)
Outdated packages with security fixes
Deprecated packages

Updates

Major version updates (breaking changes)
Minor version updates (features)
Patch updates (bug fixes)

Best Practices

Unused dependencies
Duplicate dependencies
Alternative lightweight options
ESM vs CommonJS compatibility

License Compliance

Incompatible licenses
Commercial use restrictions
Attribution requirements

Steps

Detect Package Manager
- npm / yarn / pnpm (Node.js)
- pip / poetry / pipenv (Python)
- cargo (Rust)
- go mod (Go)

Run Security Audit

npm audit
# or
pipenv check
# or
cargo audit

Check for Updates
```
npm outdated
# or
pip list --outdated
```
Identify Unused
```
npx depcheck
# or analyze imports
```

Generate Report

## Dependency Check Report

### Security Issues
| Package | Severity | Issue | Action |
|---------|----------|-------|--------|
| [pkg] | High | CVE-2024-XXXX | Update to v2.1.0 |

### Update Recommendations
| Package | Current | Latest | Priority |
|---------|---------|--------|----------|
| [pkg] | 1.0.0 | 2.0.0 | Medium |

### Unused Dependencies
- [pkg]: Can be removed

### Suggestions
- Replace [heavy-pkg] with [lightweight-alt]

Update Strategy

Immediate (Security fixes)

npm update [vulnerable-pkg]

Planned (Major versions)

Review breaking changes
Update dev dependencies first
Test thoroughly
Update production dependencies

Gradual (Minor/patch)

npm update

When to Run

Weekly/bi-weekly maintenance
Before releases
When adding new dependencies
Security incident response

Install deps-check and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# /deps-check — Dependency Check Analyze project dependencies for updates, security, and best practices. ## Check Areas ### Security - Known vulnerabilities (via `npm audit`, `safety`, etc.) - Outdated packages with security fixes - Deprecated packages ### Updates - Major version updates (breaking changes) - Minor version updates (features) - Patch updates (bug fixes) ### Best Practices - Unused dependencies - Duplicate dependencies - Alternative lightweight options - ESM vs CommonJS compatibility ### License Compliance - Incompatible licenses - Commercial use restrictions - Attribution requirements ## Steps 1. **Detect Package Manager** - npm / yarn / pnpm (Node.js) - pip / poetry / pipenv (Python) - cargo (Rust) - go mod (Go) 2. **Run Security Audit** ```bash npm audit # or pipenv check # or cargo audit ``` 3. **Check for Updates** ```bash npm outdated # or pip list --outdated ``` 4. **Identify Unused** ```bash npx depcheck # or analyze imports ``` 5. **Generate Report** ```markdown ## Dependency Check Report ### Security Issues | Package | Severity | Issue | Action | |---------|----------|-------|--------| | [pkg] | High | CVE-2024-XXXX | Update to v2.1.0 | ### Update Recommendations | Package | Current | Latest | Priority | |---------|---------|--------|----------| | [pkg] | 1.0.0 | 2.0.0 | Medium | ### Unused Dependencies - [pkg]: Can be removed ### Suggestions - Replace [heavy-pkg] with [lightweight-alt] ``` ## Update Strategy ### Immediate (Security fixes) ```bash npm update [vulnerable-pkg] ``` ### Planned (Major versions) - Review breaking changes - Update dev dependencies first - Test thoroughly - Update production dependencies ### Gradual (Minor/patch) ```bash npm update ``` ## When to Run - Weekly/bi-weekly maintenance - Before releases - When adding new dependencies - Security incident response

{ "prompt": "# /deps-check — Dependency Check\n\nAnalyze project dependencies for updates, security, and best practices.\n\n## Check Areas\n\n### Security\n- Known vulnerabilities (via `npm audit`, `safety`, etc.)\n- Outdated packages with security fixes\n- Deprecated packages\n\n### Updates\n- Major version updates (breaking changes)\n- Minor version updates (features)\n- Patch updates (bug fixes)\n\n### Best Practices\n- Unused dependencies\n- Duplicate dependencies\n- Alternative lightweight options\n- ESM vs CommonJS compatibility\n\n### License Compliance\n- Incompatible licenses\n- Commercial use restrictions\n- Attribution requirements\n\n## Steps\n\n1. **Detect Package Manager**\n - npm / yarn / pnpm (Node.js)\n - pip / poetry / pipenv (Python)\n - cargo (Rust)\n - go mod (Go)\n\n2. **Run Security Audit**\n ```bash\n npm audit\n # or\n pipenv check\n # or\n cargo audit\n ```\n\n3. **Check for Updates**\n ```bash\n npm outdated\n # or\n pip list --outdated\n ```\n\n4. **Identify Unused**\n ```bash\n npx depcheck\n # or analyze imports\n ```\n\n5. **Generate Report**\n ```markdown\n ## Dependency Check Report\n\n ### Security Issues\n | Package | Severity | Issue | Action |\n |---------|----------|-------|--------|\n | [pkg] | High | CVE-2024-XXXX | Update to v2.1.0 |\n\n ### Update Recommendations\n | Package | Current | Latest | Priority |\n |---------|---------|--------|----------|\n | [pkg] | 1.0.0 | 2.0.0 | Medium |\n\n ### Unused Dependencies\n - [pkg]: Can be removed\n\n ### Suggestions\n - Replace [heavy-pkg] with [lightweight-alt]\n ```\n\n## Update Strategy\n\n### Immediate (Security fixes)\n```bash\nnpm update [vulnerable-pkg]\n```\n\n### Planned (Major versions)\n- Review breaking changes\n- Update dev dependencies first\n- Test thoroughly\n- Update production dependencies\n\n### Gradual (Minor/patch)\n```bash\nnpm update\n```\n\n## When to Run\n- Weekly/bi-weekly maintenance\n- Before releases\n- When adding new dependencies\n- Security incident response", "variables": [], "notes": "Check dependencies for updates, vulnerabilities, and best practices", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/ZenRay/CursorTemplate", "path": ".cursor/commands/deps-check.md", "ref": "0643e2b5863ee982562d545a9276c08523c183b8", "url": "https://github.com/ZenRay/CursorTemplate/blob/0643e2b5863ee982562d545a9276c08523c183b8/.cursor/commands/deps-check.md", "key": "ZenRay/CursorTemplate/.cursor/commands/deps-check.md" } } }

deps-check

About