preen-dependency-security

To audit dependencies for vulnerabilities in a pnpm monorepo, run an automated vulnerability scan that proactively identifies high and critical security risks across all workspace packages and applies low-risk hardening fixes.

Dependency drift occurs when workspace packages use inconsistent or outdated dependency versions, creating security vulnerabilities and unstable systems that automated version hygiene and auditing can proactively detect and correct.

Fix unsafe versioning patterns like 'latest' or wildcards by running an automated dependency audit that detects these versioning risks and applies focused hardening patches to ensure reliable CI and production security.

Yes, you can automatically patch critical vulnerabilities by applying focused, low-risk hardening fixes during the audit process, ensuring production security and CI reliability without introducing breaking changes to your monorepo.

Yes, this dependency auditing and patching process is specifically designed to work within a pnpm monorepo environment, proactively scanning workspace dependencies for security vulnerabilities and version hygiene issues.

Automated dependency hardening focuses on applying low-risk fixes for high and critical vulnerabilities, meaning it may not automatically resolve major version upgrades or complex breaking changes requiring manual intervention to maintain system stability.