Do you blindly run upgrade commands when npm audit flags a vulnerability?
by•
Saw a security warning pop up during a build recently and my first instinct was just to run whatever fix command it suggested. But after having a quick look it turned out the flagged feature (some niche caching logic) wasn't even used anywhere in our codebase.
Still, updating the minor version was clean and safe so we did it anyway while leaving the rest of the dev-tool warnings alone.
It made me realize how easy it is to panic over audit logs.
How do you usually triage these warnings?
Do you patch everything immediately check if your code actually uses the affected feature or ignore moderate issues entirely?
3 views
p/many-displays
p/runevr
p/producthunt
p/google-cloud-platform
p/reso
p/kodlo
p/ai-context-flow
p/htmldrag
p/dex-by-exmergo
p/jot-2-0
p/beamfy
p/refs
p/dino-kids
p/nexupira
p/duckfightclub
p/nudgeforme
p/seshka
p/talanoa-2
p/murror
p/supabase
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.