DEV Community

loading...
Cover image for What license to use for private NPM/node or composer packages

What license to use for private NPM/node or composer packages

spekulatius1984 profile image Peter Thaleikis 🍪 Originally published at spekulatius.hashnode.dev ・1 min read

As much as I love open-source, not every project or package is meant to become open-source. Especially commercial projects are usually not released under an open-source license. For these cases you can use:

  • Private NPM/yarn packages with a license defined as "UNLICENSED" should do the trick. Make sure to not confuse it the "UNLICENSE", which is open-source.

  • Private composer packages can use the license key "proprietary" to avoid issues.

That's it. More a public note here than an article, but I guess that's fine.


Other articles of mine that you might like

Discussion (0)

pic
Editor guide