You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because this module ships with a shrinkwrap, it is impossible to avoid using the insecure braces@3.0.2, even using overrides.
Please either keep all dependencies up to date with security advisories, or remove the shrinkwrap from the deployment so that we can get security updates.
Steps to reproduce
npm install netlify-cli
npm audit
Observe that braces@3.0.2 is present in the tree, and cannot be overridden, due to the npm-shrinkwrap.json
Thanks, @isaacs. For context the impact is not very severe given the context that Netlify CLI runs in:
Affected versions of this package are vulnerable to Uncontrolled resource consumption due improper limitation of the number of characters it can handle, through the parse function. An attacker can cause the application to allocate excessive memory and potentially crash by sending imbalanced braces as input.
Yeah, it's more annoying than actually hazardous, for sure. But such is life in a world that incentivizes getting your name on a CVE more than it does the subtle nuance of actual security.
I'd really love to see the shrinkwrapping go, as it makes our live a lot harder and would let me make a very solid case for moving us off Vercel as they pin their direct dependencies while also remaining very behind the ball
Yeah... this shrinkwrap thing is getting pretty annoying. I'm awaiting a release that includes #7758 which was patched last week, but the currently available version is still shrinkwrapped to the old version of tar. With the shrinkwrap file, there's no way to npm audit --fix the vulnerability.
It's strongly discouraged for library authors to publish this file, since that would prevent end users from having control over transitive dependency updates.
The recommended use-case for npm-shrinkwrap.json is applications deployed through the publishing process on the registry: for example, daemons and command-line tools intended as global installs or devDependencies.
This is exactly the use case we have with netlify-cli.
This is an ever-growing problem. All my audit warnings are because I'm using netlify. It's a bad look! Just remove the shrinkwrap, there's no need for it.
I have fixed several really bad security vulnerabilities recently in node-tar, and you're just not allowing your users to benefit from them.
Reacted by Taylor Reece, electrovir and Gareth Jones
Not to mention you're also punishing npm users for choosing to use npm, since other package managers ignore the shrink-wrap (and by extension proving the shrink wrap can't be that important).
@isaacs I'm curious on how viable you think it would be to try and add a new .npmrc option to npm for having shrinkwraps ignored
@isaacs thanks yeah I was asking if you would think it would be tons of work to change or really straightforward, based on what you can remember of how shrinkwrapping is implemented (I assume its not load bearing, but you never know...)
I've created npm/cli#8938 to give us a place to discuss this in the more general npm context
Activity
bootstrap: remove override-thwarting shrinkwrap
merlyn-at-netlify commentedon Jul 11, 2024
Thanks, @isaacs. For context the impact is not very severe given the context that Netlify CLI runs in:
From: https://security.snyk.io/package/npm/braces/3.0.2
isaacs commentedon Jul 11, 2024
Yeah, it's more annoying than actually hazardous, for sure. But such is life in a world that incentivizes getting your name on a CVE more than it does the subtle nuance of actual security.
G-Rath commentedon Jul 26, 2024
Related:
I'd really love to see the shrinkwrapping go, as it makes our live a lot harder and would let me make a very solid case for moving us off Vercel as they pin their direct dependencies while also remaining very behind the ball
G-Rath commentedon Sep 3, 2024
there's now a new micromatch vulnerability that we cannot update due to the shrinkwrap: GHSA-952p-6rrq-rcjv
cc @sarahetter
electrovir commentedon Aug 29, 2025
This package has another vulnerability that I am unable to workaround because of
npm-shrinkwrap.json: GHSA-52f5-9888-hmc6Please stop publishing this package with
npm-shrinkwrap.json: I simply cannot use it.fix(deps): bump inquirer to resolve vulnerabilities
fix(deps): bump inquirer to resolve vulnerabilities (#7598)
G-Rath commentedon Oct 24, 2025
Have opened #7741 about another downstream vulnerability that is blocked due to the shrinkwrap
G-Rath commentedon Nov 11, 2025
... and now the use of shrinkwrap is breaking
npm cibecause of platform constraints: #7769taylorreece commentedon Nov 12, 2025
Yeah... this shrinkwrap thing is getting pretty annoying. I'm awaiting a release that includes #7758 which was patched last week, but the currently available version is still shrinkwrapped to the old version of
tar. With the shrinkwrap file, there's no way tonpm audit --fixthe vulnerability.Netlify team - any plans to remove the shrinkwrap file? NPM docs recommend against including it https://docs.npmjs.com/cli/v11/configuring-npm/npm-shrinkwrap-json
serhalp commentedon Nov 12, 2025
@taylorreece but note the previous sentence:
This is exactly the use case we have with netlify-cli.
serhalp commentedon Nov 12, 2025
🤔 No release PR was created because Dependabot marked that as
chore:. Let me look into that...isaacs commentedon Nov 12, 2025
By the way, I actually have come to feel like this is now not "merely annoying", it is actually a security issue.
If you use the netlify-cli as part of your deployment, you must have audit failures.
So you come here, find out that it's no biggie, and start ignoring it.
Now you ignore audit failures, and every time audit fails, you go "Oh, right, it's no big deal".
Which it is, until it isn't.
isaacs commentedon Jan 25, 2026
This is an ever-growing problem. All my audit warnings are because I'm using netlify. It's a bad look! Just remove the shrinkwrap, there's no need for it.
I have fixed several really bad security vulnerabilities recently in node-tar, and you're just not allowing your users to benefit from them.
forcibly remove netlify-cli so audit can pass
G-Rath commentedon Jan 25, 2026
Not to mention you're also punishing npm users for choosing to use npm, since other package managers ignore the shrink-wrap (and by extension proving the shrink wrap can't be that important).
@isaacs I'm curious on how viable you think it would be to try and add a new
.npmrcoption to npm for having shrinkwraps ignoredisaacs commentedon Jan 26, 2026
@G-Rath I think shrinkwraps were a mistake, and npm should drop support for them in the next major.
However, I no longer work on npm, so I have no more power to effect this than anyone else.
G-Rath commentedon Jan 27, 2026
@isaacs thanks yeah I was asking if you would think it would be tons of work to change or really straightforward, based on what you can remember of how shrinkwrapping is implemented (I assume its not load bearing, but you never know...)
I've created npm/cli#8938 to give us a place to discuss this in the more general npm context
isaacs commentedon Jan 27, 2026
Oh yeah, it'd be crazy easy to just stop doing shrink wraps. The hard part is just accepting the breaking change, but that's social, not technical.
chore!: stop including `npm-shrinkwrap.json`
chore(main): release 25.0.0 (#8162)
feat!: stop including `npm-shrinkwrap.json` (#8163)