And the maintainers have not re-published a fixed tarball yet and the issue remains closed. Even after the underlying issue has been fixed in npm. I think it'

And the maintainers have not re-published a fixed tarball yet and the issue remains closed. Even after the underlying issue has been fixed in npm. I think it's pretty clear which side here is acting inappropriately.