search

npms-io / npms-analyzer

The analyzer behind https://npms.io
MIT License
317 stars 38 forks source link

Transfered packages still show up in npms search as my account #219

Open adrianpraja opened 6 years ago

adrianpraja commented 6 years ago

👋

About 2 weeks ago I;ve made a request to npmjs to unpublish few npm packages from my account as they were unmaintained and some of them had misleading names;

Their action was to transfer these npm packages to the @npm user and deprecated them which had them removed from my profile and search results ( in npmjs )

However they still do show up in the npms.io search, with my name in bold 😃

These packages should not get any new hits and npms should follow npmjs practice and remove these packages from the search index

satazor commented 5 years ago

@adrianpraja Could you please list some of them so I could investigate? If you are not comfortable putting them here, you may email me directly.

adrianpraja commented 5 years ago

Sure, aws-elasticsearch is one example

https://npms.io/search?q=aws-elasticsearch

https://www.npmjs.com/package/aws-elasticsearch

satazor commented 5 years ago

@adrianpraja here's that JSON data for your package: https://registry.npmjs.org/aws-elasticsearch

We can see that it is deprecated but it doesn't contain any information saying that it belongs to @npm. I wonder how npmjs.com is hiding it from the search results, perhaps via a blacklist? @bcoe can you provide details?

adrianpraja commented 5 years ago

I see JSON does not reflect the transfer

however npm owner ls aws-elasticsearch does :)

satazor commented 5 years ago

@adrianpraja I don't know how to get the owner list as it's not available in the public registry, AFAIK. Let's wait for @bcoe feedback.

adrianpraja commented 5 years ago

Sure @satazor thanks for looking into this 👍

bcoe commented 5 years ago

@adrianpraja mind opening an issue with support[at]npmjs.com, this is probably some side-effect of how the package was transferred, and might need an engineer to dig into it.

theophilusx commented 4 years ago

I have the same issue. A transferred package which still shows up as owned by the previous owner in npms.io (the package is ssh2-sftp-client). i have sent email to support at npms.io, but have not received any replay (over 25 days ago now!). I also notice the information on the package in npms.io is way out of date (i.e. 7 months out of date). There have been numerous releases since the last time npms.io updated the package analysis. Note that npmjs.com seems to report all correct information, except for the p, q, m stats, which simply don't change.