We've talked about this in the past yet I'm not sure anything is tracking it.

Input Dev would like an API that keeps track of violations and their classes. ie; Some classes we care about are "Deprecation", "Performance", "Interop", "Input"  Currently we use console warnings to indicate hints at performance. A lot of this book keeping is done at the event or node level.

This API should take into account warning fatigue and know some information about the source of the event to prevent warning the user too much. For example for every touch event that wasn't prevent defaulted we could log a message to indicate possibly use passive event listeners. But warning on every event is troublesome and requires bookkeeping. The bookkeeping should be done in the API or filtered in the front-end view of the violations.

Paul did you have an API in mind?

Ideally we'd like to see this in devtools then we don't need to worry about is this really useful because if not it will cause fatigue.