'everything' blocks devs from removing their own NPM packages

1. guarddog

   1 6 673 9.5 Python

   :snake: :mag: GuardDog is a CLI tool to Identify malicious PyPI and npm packages

   

   Yes. https://securitylabs.datadoghq.com/articles/guarddog-identif....

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. feedback

   2 10 137 1.8

   Discontinued Public feedback discussions for npm (by npm)

   

   no-one-left-behind[1] was not even a year ago, and yet the link on npm[2] explaining why it was removed is already broken. Classic JS ecosystem.

   1: https://github.com/npm/feedback/discussions/858

   2: https://www.npmjs.com/package/no-one-left-behind

4. cli

   3 79 8,664 9.7 JavaScript

   the package manager for JavaScript (by npm)

   

   Because sometimes I make idiotic mistakes and I really don't want that embarrassing stuff out there where people can see. I ran head first into an npm bug once when I tried to symlink the README file which resulted in the thing getting published without a README.

   https://github.com/npm/cli/issues/6746

   Embarrassing. And then they slapped me with a stupid 24 hour count down on top of it. I seriously hate this thing.

Suggest a related project