deps

To audit project dependencies, this Skill checks all packages against known vulnerability databases to identify high-severity security risks. It flags outdated packages and vulnerabilities so you can apply safe patches and maintain build integrity.

To safely update npm packages, use an automated process with verification and rollback safety. This ensures build integrity through automated testing and atomic commits, rolling back updates immediately if they break the project.

Yes, you can manage dependency updates across various package managers. The Skill supports universal actions like audit, update, add, remove, and outdated checks, allowing you to maintain project integrity regardless of the specific package manager used.

Package management tools handle atomic commits by bundling dependency updates into single, indivisible transactions paired with automated testing. This ensures safe versioning and allows the system to cleanly roll back changes if the updated package breaks build integrity.

You should not use automated dependency updates when a project lacks automated testing, as safe updates rely on test verification to ensure build integrity. Additionally, avoid it if your workflow requires manual review of package versioning before modifying package managers.