of course not. but you're setting a precedent may...
# core
g
of course not. but you're setting a precedent maybe tables like that belong in osquery core, maybe not. the code is objectively good, and the data in the new table is useful, but it's still good to discuss wether this kind of table should live in osquery (vs in an extension or in a server side data pipleline)