The license must not discriminate against any person or group of persons.
That is the legal definition to be compliant as per OSI. The JSON license did not fulfill it. However, since then, the JSON spec/schema has been worked out under ECMA 5 standardisation, so you can JSON for all your evil projects now without a worry. [1]
JSLint, however, you will need to get a waiver like IBM did.[2]
Yep, there have been many arguments on Debian that it isn't disributable as it isn't compatible with DFSG (Debian Free Software Guidelines).
Also, google code hosting removed it as it wasn't Free Software... which was quite ironic given their 'do no evil' stance.
The real issue is... few 'bad people' think they are evil, and therefore it is too subjective. Licences are not the place to make silly clauses, if you want the main premise to be respected.
https://opensource.org/osd
The license must not discriminate against any person or group of persons.
That is the legal definition to be compliant as per OSI. The JSON license did not fulfill it. However, since then, the JSON spec/schema has been worked out under ECMA 5 standardisation, so you can JSON for all your evil projects now without a worry. [1]
JSLint, however, you will need to get a waiver like IBM did.[2]
[1]: https://news.ycombinator.com/item?id=3693108
[2]: http://dev.hasenj.org/post/3272592502/ibm-and-its-minions