tools to check/track (code) compliance

[Bradley M. Kuhn]

Trevor Woerner wrote:
>> Another method might be to use a tool which analyses the code itself
>> (i.e. the code which is committed) looking for indications that the
>> code might be from somewhere else (e.g. different coding style,
>> copyright statements, license files, etc.).

While it doesn't completely serve your needs, you should definitely look
at FOSSology, which is (AFAIK) completely Free Software.  It just
catalogs what it can find with regard the licensing and copyright
information in files, and doesn't try to make assessments.  

Peter is quite correct that this is a very hard technical problem in the
abstract.  I've looked into it myself a few times and the issue of false
positives is very bad.  I believe we won't get something good until
there is a real Free Software project trying to do it.  I think
FOSSology wants to go there eventually, and I hope developers will help
them do it.
-- 

   -- bkuhn