Missing license about password_compat HOT 6 CLOSED

That's a very good point. Since this is a derivative work of the PHP core implementation, the PHP license should apply.'ve updated the relevant files.

from password_compat.

Using PHP license makes sense, but it's incompatible with GPL, so many (open source) projects won't be able to use it.

from password_compat.

I agree with @gergoerdosi , MIT allowed broader adoption. In fact, I completely missed the "MIT" mention in composer.json before submitting this issue. I was looking for a LICENCE file, and/or a licence header comment in the code. Not sure if composer.json is visible enough (at least it wasn't for me :) )

from password_compat.

I did some research and found that PHP licensed code can be distributed in a GPL application, the distributor just needs to add an exception to the license. I would consider dual licensing this code though (PHP and GPL), so it would be easier to use it in projects.

from password_compat.

Or use MIT as @nicolas-grekas suggests, it's GPL compatible.

from password_compat.

I've reverted it back to the MIT license. I wanted to use the PHP license, because it's a derivative of the core implementation. But at the same time, I own that copyright, so I can relicense it as I see fit. So I'm putting it out as MIT.

from password_compat.