Hi -

A skill or agent that helps with assembling the LICENSE, NOTICE, and 
.rat-excludes file gives a good way to focus on what humans should check in the 
source code. I think that an agreed tool that uses an MCP on legal-discuss@ and 
general@ could really help projects do their diligence often - from a periodic 
workflow, but not from CI on every PR (we don’t have the budget for the number 
of tokens that would take).

Once such a skill and agent exists and is proven I would add this to ATR as one 
of the checks that is always done. It would be adjacent to the RAT check 
already done and would provide an important adjunct to the LICENSE and NOTICE 
checks which are not much more than existence checks.

SBOM tools and some of the databases the ecosystem is building are a good 
start, but again the license annotations and whether a dependency with multiple 
licenses is an OR or an AND needs a check. On top of that a dependency’s 
license could be changed. There are also additional risk based considerations 
with dependencies like is it maintained? In ATR’s presentation of SBOM 
information we are trying to highlight concerns and we acknowledge that some of 
these are bad data and missing mappings.

Best,
Dave

> On Sep 9, 2026, at 8:50 AM, Justin Mclean <[email protected]> wrote:
> 
> Hi,
> 
> Automation cannot solve this problem; it only solves part of it. We have RAT, 
> and most projects run it as part of their build.
> 
> I've been reviewing incubator releases for well over a decade, and the issues 
> I raise are not ones RAT would have caught. A recent candidate used HawkEye, 
> the PPMC voted +1 and found no issues, and the IPMC voted -1 because of valid 
> issues.
> 
> Header checks and dependency scans are good at what they cover. They don't 
> tell you whether a bundled dependency's license is compatible, whether NOTICE 
> says the right thing, or whether a file with a correct-looking header is 
> genuinely under that license. A release can pass all of them and still ship 
> GPL-licensed code, this has happened more than once.
> 
> Tools narrow down what a reviewer has to look at, but they don't remove the 
> reviewer, and we cannot 100% automate this.
> 
> Kind regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to