Install
openclaw skills install cuihua-dependency-updater๐ฆ AI-powered dependency update assistant. Intelligently update npm/yarn packages with safety checks, breaking change detection, and automated testing. Keep dependencies fresh without breaking your app.
openclaw skills install cuihua-dependency-updaterKeep dependencies fresh, keep your app safe
AI-powered dependency management that updates packages intelligently:
The problem:
npm outdated shows 50+ packages to updatecuihua-dependency-updater solves this.
"Check outdated dependencies"
Output:
๐ฆ Dependency Update Report
โโโโโโโโโโโโโโโโโโโโโโโโ
๐ด Security updates (3):
- lodash: 4.17.19 โ 4.17.21 (CVE-2020-8203)
- minimist: 1.2.5 โ 1.2.6 (CVE-2021-44906)
- axios: 0.21.1 โ 1.6.0 (CVE-2023-45857)
๐ก Breaking changes (2):
- webpack: 4.46.0 โ 5.89.0 (Major version)
- react: 17.0.2 โ 18.2.0 (Major version)
๐ข Safe updates (12):
- typescript: 4.9.5 โ 5.3.3 (Minor)
- eslint: 8.50.0 โ 8.56.0 (Patch)
...
๐ก Recommendation: Update security first
"Update security vulnerabilities"
Generated:
npm update lodash minimist axios
npm audit fix
"Update all safe dependencies"
Automatically:
Updates are categorized by risk and impact:
{
"security": [
{ package: "lodash", severity: "high", cve: "CVE-2020-8203" }
],
"breaking": [
{ package: "webpack", from: "4.x", to: "5.x", impact: "high" }
],
"safe": [
{ package: "typescript", from: "4.9", to: "5.3", impact: "low" }
]
}
AI analyzes changelogs and API changes:
โ ๏ธ Breaking changes detected in react@18:
1. ReactDOM.render โ createRoot
Impact: ALL entry points need updates
2. Automatic batching
Impact: State updates may batch differently
3. Stricter hydration
Impact: SSR apps may break
Recommendation: Schedule major update separately
Estimated effort: 2-4 hours
Integrates with npm audit and vulnerability databases:
๐ด HIGH severity vulnerability
โโโโโโโโโโโโโโโโโโโโโโโโโโโ
Package: lodash@4.17.19
CVE: CVE-2020-8203
Severity: HIGH
Impact: Prototype pollution
Affected paths:
- app โ lodash (direct)
- webpack โ lodash (indirect)
Fix available: lodash@4.17.21
Risk: LOW (patch version)
๐ Safe to update immediately
Run tests after each update batch:
async function safeUpdate(packages) {
// Backup current state
const backup = await saveState();
try {
// Update packages
await npm.update(packages);
// Run tests
const testsPassed = await runTests();
if (!testsPassed) {
throw new Error('Tests failed');
}
console.log('โ
Update successful');
} catch (error) {
// Rollback on failure
await restore(backup);
console.log('โฎ๏ธ Rolled back due to:', error.message);
}
}
Auto-generate human-readable update summaries:
# Dependency Updates - 2026-03-24
## Security Fixes (3)
- lodash: 4.17.19 โ 4.17.21
- Fixed: Prototype pollution vulnerability
- CVE: CVE-2020-8203
- axios: 0.21.1 โ 1.6.0
- Fixed: SSRF vulnerability
- CVE: CVE-2023-45857
## Feature Updates (5)
- typescript: 4.9.5 โ 5.3.3
- Added: Better type inference
- Added: Decorators support
- eslint: 8.50.0 โ 8.56.0
- Fixed: Several bugs
- Added: New rules
## Breaking Changes (Postponed)
- webpack: 4.46.0 โ 5.89.0
- Reason: Requires configuration migration
- Estimated effort: 4 hours
- Scheduled: Next sprint
User: "Audit dependencies for security issues"
Agent:
๐ Security Audit Report
โโโโโโโโโโโโโโโโโโโโโโ
Total packages: 1,234
Vulnerabilities: 8
๐ด CRITICAL (1)
- express-fileupload@1.1.7
CVE-2020-7699 (RCE)
Fix: Update to 1.4.0
๐ HIGH (3)
- lodash@4.17.19 โ 4.17.21
- minimist@1.2.5 โ 1.2.6
- axios@0.21.1 โ 1.6.0
๐ก MEDIUM (4)
- qs@6.5.2 โ 6.11.0
- ...
๐ก Action: npm audit fix --force
Risk: All fixes are patch/minor versions
User: "Can I safely update React to v18?"
Agent:
๐ Analyzing React 17 โ 18 migration...
โ
Compatibility Check:
- react-dom: Compatible
- react-router: Needs update to v6
- redux: Compatible
- typescript: Compatible
โ ๏ธ Breaking Changes:
1. ReactDOM.render API removed
Files affected: 2 (src/index.js, src/test-utils.js)
2. Automatic batching changes
Potential impact: State update timing
3. Stricter TypeScript types
Files affected: 15
๐ Migration complexity: MEDIUM
Estimated time: 2-3 hours
Recommendation: Update in separate PR
๐ง Migration steps:
1. Update packages
2. Replace ReactDOM.render
3. Fix TypeScript errors
4. Test thoroughly
Want me to generate a migration guide?
User: "Update all safe dependencies"
Agent:
๐ฆ Preparing batch update...
Grouped into 3 batches:
Batch 1 (Testing tools - 5 packages):
- jest: 29.5.0 โ 29.7.0
- @testing-library/react: 14.0.0 โ 14.1.2
- ...
Batch 2 (Build tools - 4 packages):
- vite: 5.0.0 โ 5.0.10
- esbuild: 0.19.0 โ 0.19.11
- ...
Batch 3 (Utils - 8 packages):
- date-fns: 2.30.0 โ 3.0.6
- lodash: 4.17.19 โ 4.17.21
- ...
Process:
1. Update Batch 1 โ Run tests โ โ
2. Update Batch 2 โ Run tests โ โ
3. Update Batch 3 โ Run tests โ โ
โ
All updates successful!
๐ Changelog: UPDATES.md
Create .dependencyrc.json:
{
"updateStrategy": "conservative",
"priorities": [
"security",
"patch",
"minor",
"major"
],
"autoUpdate": {
"security": true,
"patch": true,
"minor": false,
"major": false
},
"testing": {
"runTests": true,
"testCommand": "npm test",
"rollbackOnFail": true
},
"exclude": [
"react",
"webpack"
],
"changelog": {
"generate": true,
"path": "./UPDATES.md"
}
}
Define your own rules per package:
{
"packages": {
"lodash": "aggressive",
"react": "manual",
"typescript": "conservative"
}
}
MIT
Built with ๐ธ by ็ฟ ่ฑ (Cuihua)
Made with ๐ธ | Cuihua Series | ClawHub Pioneer
Keep dependencies fresh, keep your app safe.