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
{{ message }}
Repository navigation
Consider a new v2 release addressing the npm audit issues #212
tl:dr; npm audit is unhappy with node-tar@^2 because of https://hackerone.com/reports/344595. Since node-tar@^2 is used in node-gyp the npm audit alert is rippling throughout the Node community. Bumping to node-tar@^4 breaks Node 0.10 & 0.12 support which starting up the typical semver debates, and may force a lot of projects to subsequently bump their majors, and so on an do fourth.
Edit: node-tar@^2 not @^3
Reacted by ArstanWhitebeard, Iain van der Wiel, Jared Hobbs, Tayllan Búrigo, Wenchen Li, Juliana Peña, Nick Schonning, @brody2consult - Chris J. Brody, Nikita Skovoroda, Tristan Deering and 17 more
changed the title [-]Consider a new v3 release addressing the npm audit issues[/-][+]Consider a new v2 release addressing the npm audit issues[/+]on Apr 23, 2019
There are a lot of libs chain-depending on tar@2, and they get reports from npm audit now.
Even npm itself does, 4 times in different chains:
+ npm@6.9.0added 426 packages from 800 contributors and audited 12096 packages in 5.679sfound 4 high severity vulnerabilities run `npm audit fix` to fix them, or `npm audit` for details
That's essentially a false positive, because anyone in position to exploit node-tar in that dependency chain is most likely also in position to just ship malicious code.
But that's a signal that is deminishing value from future valid npm audit reports, which is not a very good thing to do. /cc @isaacs
node-gyp can't update node-tar to v4.x without doing a semver-major version bump because of node-tar changing the supported platforms version.
So, unless a fixed node-tar version is released in 2.x branch, downstream (including npm, npm-lifecycle etc) would have to do a major version bum for node-gyp.
Another possible way forward would be to migrate node-gyp@3 off node-tar usage completely, but that is not the ideal solution.
I would gladly accept a PR against the v2 branch to address this. But I'm not really interested in doing work to support node versions long past their LTS expirations. The library has been completely rewritten since then, so it's not a simple backport. If anyone wants to take this on, I'll be happy to answer any questions and publish it once it lands, but I haven't even looked at that version of the codebase for 2 years now.
Reacted by Nikita Skovoroda, Stuart Begg, Nicolas HENRY, Victor Ferraz, Jordan Tucker, Eric Defore, Damien Retzinger and Donny Mellstrom
@isaacs Thanks for the fast reply! (Also, for the willingness to accept a patch and cut a release).
But I'm not really interested in doing work to support node versions long past their LTS expirations.
I believe that that's not the point, the point is that npm audit is going to emit false positive high severity warnings on everything, including npm itself, until either of these happens (example is for npm itself):
a fixed v2.x version is released,
a semver-major version of node-gyp is released (done), and new versions of npm-lifecycle and npm (and pretty much everything else for packages other than npm) are released to address that semver-major version bump.
I've been digging into the v2 code this morning, and I'm not sure v2 is actually vulnerable to this attack. In v2, when an extract encounters a link, it runs this code (lines 46-49 in lib/extract.js):
And a comment above this code explains the reasoning behind this:
// Hardlinks in tarballs are relative to the root
// of the tarball. So, they need to be resolved against
// the target directory in order to be created properly.
However, I believe this results in a buggy implementation of tar extraction. Here's an example:
I have a sample tar, archive.tar, and running tar tvf archive.tar yields the following output:
Error: ENOENT: no such file or directory, link '/some-path/node-tar/extracted/extracted/two.txt' -> '/some-path/node-tar/extracted/one.txt'
I believe the root cause of this issue is that the linkpath contained in the entry for one.txt is changed from ./two.txt to extracted/two.txt by the previously mentioned if statement (and this can be confirmed with a few logs). Removing the above if statement, this extraction works as expected.
So, from what I can tell, tar extraction with hard links in v2 is buggy, but it isn't actually vulnerable to this attack.
Side note: if you comment out the if statement included above, the attack does work.
EDIT: I did some digging through the v2.x.x tags, and all of them have the above if statement in lib/extract.js. So, if this piece of code truly does keep the attack from working (even though it does create other bugs), no 2.x.x versions would be vulnerable.
/cc @vdeturckheim, perhaps, re: 2.x being affected or not
Upd: It looks like 2.x still overwrites files inside the dest dir. That's not what patched 4.x does.
Also, I am not completely sure if that's not exploitable to overwrite files outside of the dest dir, I didn't take a close enough look yet.
After more experimenting I can also confirm that 2.x.x can still overwrite files inside the destination directory. However, I don't think it's possible to overwrite files outside of the destination directory because of the inner path.join on line 48:
path.join("/",entry.props.linkpath)
The result of the above path.join will always be something like the following:
/some/path/here
And this path can't have any ..s in it because the path.normalize run internally by path.join will resolve them. So, when the outside path.join runs on line 48, the arguments will be something like this:
path.join('target','/some/path/here')
And this will always result in a path inside the target directory because the second argument can't have any ..s in it.
Reacted by Jimmy Brawn, Yoshi, Wilgert Velinga and Tyler Levine
Can we get this looked at sooner than later please?
Reacted by Ankur Kaushal, Dan Mosedale, Oliver Klee, Gwyn J, William DA SILVA, Gunnar Mills , Hoang Nguyen, Kristie Giles, Der Mundschenk & Compagnie, Patrick Conrey and 31 more
Ok, there's a v2.2.2 which no longer has this vulnerability, and includes a test to verify.
Fixed on this commit in fstream: npm/fstream@6a77d2f which is published on fstream@1.0.12
Let's get this tested in node-gyp, update the advisory, and put this to bed.
Reacted by Nick Schonning, Brian Kurek, Giuseppe Criscione, Michael Mifsud, Donna Hogan, Timothy Lee, Jordan Harband, Tom Thorogood, Henrik Rypkema, Raffi Bagdasarian and 7 more
npm advisory will be updated tomorrow morning, and then npm audit fix will Just Work for anyone hitting this due to node-gyp, since it's a patch version. This is a patch in a legacy version that's been broken for a pretty long time, so it seems hard to make the case that it should be an urgent emergency.
(I swear to god if someone comes out of the woodwork demanding this be backported to tar@v1, I'm gonna have to be rushed to the hospital, this code is so old and so gnarly. The tests don't even run properly on any version of node newer than v4.)
Reacted by Cameron, Donna Hogan, Chris Collins, Henrik Rypkema, louptony, Pierre-Do Putallaz, Matt Norton, Raffi Bagdasarian, Alex Cabrera, Thomas Parisot and 35 more
Reacted by Jordan Harband, Tom Thorogood, Nick Schonning, Henrik Rypkema, louptony, Alex Cabrera, Thomas Parisot, Yves M., Amr Salama, patrikjuvonen and 14 more
Reacted by Donna Hogan, mart cube, Henrik Rypkema, louptony, Brian Merlob, Alex Cabrera, Thomas Parisot, Benny, Yves M., François Clément and 19 more
Reacted by Ben Löffel, Henry Blyth, Nikita Skovoroda, lucas d'urso, Alan Agius, Adonis Kakoulidis, Dan Manastireanu, Braian Silva, Donna Hogan, Alex and 4 more
Reacted by Yves M., François Clément, Amr Salama, Henry Blyth, Adonis Kakoulidis, Donna Hogan, Alex, Braian Silva and Kevin van Rijn
The advisory has been updated as of this morning. npm audit fix should address this without any issue now, as long as you're on either the 2.x or 4.x tar versions.
Reacted by Giuseppe Criscione, Jordan Harband, Shaun Collins, Nikita Skovoroda, Torsten Stüber and Nathan Babcock
Got it resolved! sorry guys... i had a node-gyp dependency for npm-lifecycle, once I resolved, the manual review on fstream dependencies could be fixed quickly! It works now! :) 👍
I contacted NIST directly about 2.2.2 not having the vulnerability, and got the following response:
After review of the CVEs, the information provided, and the configurations we have made the appropriate modifications. Please allow up to 24 hours for these changes to populate on the website and in the data feeds.
So stay tuned, because soon 2.2.2 will be recognized as an acceptable, non-vulnerable version, and appropriate versions of dependent packages like node-gyp will no longer be flagged as vulnerable.
Reacted by Yves M., callan-stretton and Matthew Leffler
Reacted by callan-stretton
Reacted by Vinayak Kulkarni, Brian Surowiec, Tom Thorogood, nx, Jonathan Beliën, Yves M., patrikjuvonen, callan-stretton and Matthew Leffler
There's a new version, but it seems to be uninstallable.
If you:
mkdir t
cd t
npm init
npm install semantic-release
You'll get errors about tar and fstream being out of date. npm audit fix will say "12 out of 12 problems fixed", but then npm install will tell you there are still 12 problems. The dependency that keeps installing tar@2.2.1 is node-gyp@3.8.0, and it wants:
"tar": "^2.0.0",
So it should be getting 2.2.2. The complete dependency tree for tar is:
So, with great irony, npm appears to indirectly be part of the problem why I'm getting an old version of tar. -_- The only way to get 2.2.2 seems to be to manually edit my package-lock.json file.
There's a new version, but it seems to be uninstallable.
It is installable, except npm is using bundledDependencies, so in effect it is the same as having it locked. Hopefully there's a new release of npm soon.
Activity
stof commentedon Apr 23, 2019
node-gyp is using node-tar@2, not node-tar@3 though. So what is needed would be a new v2 release.
xzyfer commentedon Apr 23, 2019
[-]Consider a new v3 release addressing the npm audit issues[/-][+]Consider a new v2 release addressing the npm audit issues[/+]ChALkeR commentedon Apr 23, 2019
There are a lot of libs chain-depending on
tar@2, and they get reports fromnpm auditnow.Even
npmitself does, 4 times in different chains:That's essentially a false positive, because anyone in position to exploit node-tar in that dependency chain is most likely also in position to just ship malicious code.
But that's a signal that is deminishing value from future valid
npm auditreports, which is not a very good thing to do. /cc @isaacsnode-gypcan't updatenode-tarto v4.x without doing a semver-major version bump because of node-tar changing the supported platforms version.So, unless a fixed node-tar version is released in 2.x branch, downstream (including npm, npm-lifecycle etc) would have to do a major version bum for
node-gyp.Another possible way forward would be to migrate node-gyp@3 off node-tar usage completely, but that is not the ideal solution.
isaacs commentedon Apr 23, 2019
I would gladly accept a PR against the v2 branch to address this. But I'm not really interested in doing work to support node versions long past their LTS expirations. The library has been completely rewritten since then, so it's not a simple backport. If anyone wants to take this on, I'll be happy to answer any questions and publish it once it lands, but I haven't even looked at that version of the codebase for 2 years now.
ChALkeR commentedon Apr 23, 2019
@isaacs Thanks for the fast reply! (Also, for the willingness to accept a patch and cut a release).
I believe that that's not the point, the point is that
npm auditis going to emit false positive high severity warnings on everything, includingnpmitself, until either of these happens (example is fornpmitself):semver-major version of(done), and new versions ofnode-gypis releasednpm-lifecycleandnpm(and pretty much everything else for packages other thannpm) are released to address that semver-major version bump.ChALkeR commentedon Apr 24, 2019
See e.g. npm/npm-lifecycle#28
BRKurek commentedon Apr 24, 2019
I've been digging into the v2 code this morning, and I'm not sure v2 is actually vulnerable to this attack. In v2, when an extract encounters a link, it runs this code (lines 46-49 in
lib/extract.js):And a comment above this code explains the reasoning behind this:
However, I believe this results in a buggy implementation of tar extraction. Here's an example:
I have a sample tar,
archive.tar, and runningtar tvf archive.taryields the following output:So the tar simply consists of two files:
two.txtandone.txtwhereone.txtis a hard link totwo.txt.Using the v2 node-tar branch locally, I ran the following script:
And got the following error:
I believe the root cause of this issue is that the
linkpathcontained in the entry forone.txtis changed from./two.txttoextracted/two.txtby the previously mentioned if statement (and this can be confirmed with a few logs). Removing the above if statement, this extraction works as expected.So, from what I can tell, tar extraction with hard links in v2 is buggy, but it isn't actually vulnerable to this attack.
Side note: if you comment out the if statement included above, the attack does work.
EDIT: I did some digging through the v2.x.x tags, and all of them have the above if statement in
lib/extract.js. So, if this piece of code truly does keep the attack from working (even though it does create other bugs), no 2.x.x versions would be vulnerable.ChALkeR commentedon Apr 24, 2019
/cc @vdeturckheim, perhaps, re: 2.x being affected or not
Upd: It looks like 2.x still overwrites files inside the dest dir. That's not what patched 4.x does.
Also, I am not completely sure if that's not exploitable to overwrite files outside of the dest dir, I didn't take a close enough look yet.
Thoughts?
BRKurek commentedon Apr 24, 2019
After more experimenting I can also confirm that 2.x.x can still overwrite files inside the destination directory. However, I don't think it's possible to overwrite files outside of the destination directory because of the inner
path.joinon line 48:The result of the above
path.joinwill always be something like the following:And this path can't have any
..s in it because thepath.normalizerun internally bypath.joinwill resolve them. So, when the outsidepath.joinruns on line 48, the arguments will be something like this:And this will always result in a path inside the target directory because the second argument can't have any
..s in it.BRKurek commentedon Apr 27, 2019
Opened #213 with a potential solution to this vulnerability.
yoshiedm commentedon May 1, 2019
@isaacs, @xzyfer and other contributors, would you be able to review @BRKurek 's PR?
Thanks!
AzRu commentedon May 3, 2019
Can we get this looked at sooner than later please?
Bump fstream to fix hardlink overwriting vulnerability
isaacs commentedon May 15, 2019
Ok, there's a v2.2.2 which no longer has this vulnerability, and includes a test to verify.
Fixed on this commit in fstream: npm/fstream@6a77d2f which is published on fstream@1.0.12
Let's get this tested in node-gyp, update the advisory, and put this to bed.
isaacs commentedon May 15, 2019
npm advisory will be updated tomorrow morning, and then
npm audit fixwill Just Work for anyone hitting this due to node-gyp, since it's a patch version. This is a patch in a legacy version that's been broken for a pretty long time, so it seems hard to make the case that it should be an urgent emergency.(I swear to god if someone comes out of the woodwork demanding this be backported to tar@v1, I'm gonna have to be rushed to the hospital, this code is so old and so gnarly. The tests don't even run properly on any version of node newer than v4.)
xzyfer commentedon May 15, 2019
Thank you
Revert tar resolution
vinayakkulkarni commentedon May 15, 2019
Fixes sass/node-sass#2625
isaacs commentedon May 15, 2019
The advisory has been updated as of this morning.
npm audit fixshould address this without any issue now, as long as you're on either the 2.x or 4.x tar versions.TorstenStueber commentedon May 15, 2019
Will this also be updated automatically? https://nvd.nist.gov/vuln/detail/CVE-2018-20834
Seems that this is what github bases its vulnerability reports on.
trupti11 commentedon May 15, 2019
Hi @isaacs , I just tried this, and it still doesn't fix my problems doing npm audit fix. I had tar version 4.4.8, but i also tried downgrading it to 4.4.2; Please can you help?
──────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libcipm > npm-lifecycle > node-gyp > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libcipm > npm-lifecycle > node-gyp > tar > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libnpm > npm-lifecycle > node-gyp > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libnpm > npm-lifecycle > node-gyp > tar > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > node-gyp > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > node-gyp > tar > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > npm-lifecycle > node-gyp > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=1.0.12 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > npm-lifecycle > node-gyp > tar > fstream │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/886 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=2.2.2 <3.0.0 || >=4.4.2 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libcipm > npm-lifecycle > node-gyp > tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/803 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=2.2.2 <3.0.0 || >=4.4.2 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libnpm > npm-lifecycle > node-gyp > tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/803 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=2.2.2 <3.0.0 || >=4.4.2 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > node-gyp > tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/803 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Arbitrary File Overwrite │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=2.2.2 <3.0.0 || >=4.4.2 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > npm-lifecycle > node-gyp > tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/803
trupti11 commentedon May 15, 2019
Got it resolved! sorry guys... i had a node-gyp dependency for npm-lifecycle, once I resolved, the manual review on fstream dependencies could be fixed quickly! It works now! :) 👍
vinayakkulkarni commentedon May 16, 2019
erikeckhardt commentedon May 22, 2019
I contacted NIST directly about 2.2.2 not having the vulnerability, and got the following response:
So stay tuned, because soon 2.2.2 will be recognized as an acceptable, non-vulnerable version, and appropriate versions of dependent packages like node-gyp will no longer be flagged as vulnerable.
Update dependencies; tar@2.2.2 is NOT VULNERABLE
jwalton commentedon May 28, 2019
There's a new version, but it seems to be uninstallable.
If you:
You'll get errors about tar and fstream being out of date.
npm audit fixwill say "12 out of 12 problems fixed", but thennpm installwill tell you there are still 12 problems. The dependency that keeps installing tar@2.2.1 is node-gyp@3.8.0, and it wants:So it should be getting 2.2.2. The complete dependency tree for tar is:
So, with great irony, npm appears to indirectly be part of the problem why I'm getting an old version of tar. -_- The only way to get 2.2.2 seems to be to manually edit my package-lock.json file.
dominykas commentedon May 28, 2019
It is installable, except npm is using
bundledDependencies, so in effect it is the same as having it locked. Hopefully there's a new release of npm soon.tool-tip, fixing npm issues, tar warning is false positive isaacs/nod…