This borderline seems like a license trap: use common keywords as your package name to boost visibility, post it on NPM (with the license truncated so much as t

This borderline seems like a license trap: use common keywords as your package name to boost visibility, post it on NPM (with the license truncated so much as to be useless[1]), and then wait for an unsuspecting developer to pull in the package so you can file suit. [0] https://www.npmjs.com/package/@react-pdf-viewer/core https://www.npmjs.com/package/@react-pdf-viewer/core [1] On a 4K screen, the most I can see of it is "https://react-pdf-vie https://react-pdf-vie..."