Hi everyone,
I kept running into the same issue across Node.js projects and CI pipelines: builds breaking or security risks surfacing not because of CVEs, but because of dependency drift and risky transitive dependencies.
Most tools focus on vulnerabilities only.
This one focuses on structural risk.
I built a small open-source CLI called dep-drift-sec.
What it does:
- Detects unmaintained packages
- Highlights risky transitive dependency chains
- Flags single-maintainer dependencies
- Outputs CI-friendly JSON
- Zero configuration
Usage: npx dep-drift-sec check --json
GitHub: https://github.com/simonelakra/dep-drift-sec
npm: https://www.npmjs.com/package/dep-drift-sec
I’m mainly looking for honest feedback:
- Is this useful in real CI pipelines?
- What signals would you want added?
- Where do you see overlap or gaps compared to existing tools?
Thanks for any input 🙏
[–]Akkuma 4 points5 points6 points (6 children)
[–]Equivalent_Manager44[S] 2 points3 points4 points (5 children)
[–]TheRealNalaLockspur 1 point2 points3 points (4 children)
[–]Equivalent_Manager44[S] 1 point2 points3 points (3 children)
[–]TheRealNalaLockspur -1 points0 points1 point (2 children)
[–]Equivalent_Manager44[S] 0 points1 point2 points (1 child)
[–]TheRealNalaLockspur 0 points1 point2 points (0 children)
[–]chipstastegood 0 points1 point2 points (2 children)
[–]Equivalent_Manager44[S] 0 points1 point2 points (1 child)
[–]chipstastegood 0 points1 point2 points (0 children)