-
Notifications
You must be signed in to change notification settings - Fork 14
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
[BUG] Cannot convert undefined or null to object when running security advisory #12
Comments
I just ran into this on a different package. I believe this is the issue the open PR #7 would resolve. I'm also still looking for any detail that would indicate whether this is an npmjs.org bug or if there's a valid workaround at some level. It sounds like "unpublished packages" may be the key phrase to look for? |
In my case, I resurrected a package that someone had removed from npm (unpublished). I'm referencing a copy directly from a git repository now. Because the name is the same as the original and npmjs serves details for unpublished packages now (with a different/shorter schema), when the npm cli runs the audit it downloads that minimal "unpublished" package file (packument) from npmjs and explodes. In my particular case, renaming the package worked around the issue because I have source access. I assume another workaround would be to publish a package with npmjs (is un-unpublishing a thing?). |
@tarwn thanks for your answer, I think will try to rename package to solve this problem. |
Also ran into this with a clone of atom, npm version 8.3.1 Here's the log:
|
Closing as a duplicate of npm/cli#4313 |
What / Why
When
Where
How
Current Behavior
Steps to Reproduce
Expected Behavior
Who
References
I compare registry data between
cordova-plugin-openwith
and other package I can install without error foundcordova-plugin-openwith
got different format. It doesn't containversions
field cause advisory try to get keys from undefined.metavuln-calculator/lib/advisory.js
Line 102 in 8575e2b
registry data reference
The text was updated successfully, but these errors were encountered: