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
I have read most of the list of known issues before filing this issue.
I have searched for similiar issues before filing this issue. (took a quick look, though)
This is an enhancement request: Due to a security vulnerability message of a dependency package, I took a look at the issue and understand the injection has been performed by a different person, not by the creator of the library.
Original author drops maintaining the library, then someone wants it, he hands it over. The new guy implements a malicious code, publishes it. Currently even the original author has no publish rights on npm.
What I could think of is that: npm-check-updates might warn us when owner is changed, like in the way:
************************************ WARNING ******************************************
This repository's owner has changed. You are advised to check on the new owner.
Please type the new owner's mail address to continue: ...
************************************ WARNING ******************************************
The text was updated successfully, but these errors were encountered:
This is an enhancement request: Due to a security vulnerability message of a dependency package, I took a look at the issue and understand the injection has been performed by a different person, not by the creator of the library.
Original author drops maintaining the library, then someone wants it, he hands it over. The new guy implements a malicious code, publishes it. Currently even the original author has no publish rights on npm.
What I could think of is that: npm-check-updates might warn us when owner is changed, like in the way:
The text was updated successfully, but these errors were encountered: