-
Notifications
You must be signed in to change notification settings - Fork 47.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create-react-class has vulnerable pkg dependencies #19840
Comments
Thanks for your concern. As you can see, there's no actual vulnerability affecting |
Could a new release of create-react-class be made with an updated fbjs, if a isomorphic-fetch 2.x patch is not made? |
I created an issue there facebook/fbjs#402 |
Yes, and as I've said:
We need a patch, not a major version. |
Again, just to be clear, we are not talking about an actual vulnerability. This is a false positive for If this were an actual vulnerability, it would be a high priority to figure out and fix asap. But since this is a false positive for |
Seems like it would be good practice to have Also seems like newer react uses "shared" to get dependencies like invariant instead of using fbjs https://github.com/facebook/react/blob/master/packages/shared/invariant.js this seems like a better approach. |
Any update on this? |
The "ecosystem" is not fixing this, a new build of |
I've suggested earlier that |
@gaearon on the specific reason why a major version was released was because of upstream dependencies on isomorphic-fetch:
the author was being safe to not break consumers. which means create-react-class and fbjs would need to do the same. unless you can come up with a compelling reason for isomorphic-fetch to potentially break users with a patch version? |
Thanks, guys! Unfortunately, I'm using a package that depends on |
I’m afraid I don’t understand the argument. I am not proposing to break anyone in a patch. Somewhere at the edge, there was a vulnerability. Which package was this? And which release was the vulnerability fixed in? If the initial vulnerability source only released a major version, that’s a problem. While it’s not always possible, ideally (especially for a small fix) it should be backported as a patch. Precisely so that people can get the fixed version without risking a major upgrade. I’d like to better understand what happened here. Can you help me find which package initially patched the vulnerability? Then we can look if it was intentionally not released in the patch form, and why. |
Yes there is a codemod. |
Thanks, @gaearon. Much appreciated! |
@gaearon maybe you can talk to @matthew-andrews on this thread: matthew-andrews/isomorphic-fetch#189 I have asked him to do a patch release but there has been no update |
All right, I put out |
Thanks @gaearon!!! |
Can you verify it works? I did it by hand. |
@Gaeron of course the vuln warning is gone now that |
The latest package of create-react-class pulls in an older version of fbjs which pulls in dependencies that have vulnerabilities.
React version:
create-react-class@15.6.3
The text was updated successfully, but these errors were encountered: