There's two kinds of license compatibility one might care about, relicensing compatibility and license merging compatibility (“can a project using a particular license adopt components with another license with no effect on the restrictions imposed downstream” [a somewhat weaker form of this that is unconcerned with additional notice requirements that have no substantive effect on what downstream users can do is perhaps the more common form] vs. “can a project use upstream component under one license simultaneously with upstream components under another license at all”). JSLint has license merging compatibility with some F/OSS licenses, but not even the weaker form of relicensing compatibility (although permissive license will often have at least the weaker form of relicensing compatibility going to the JSLint license.)