A maintainer who is the only person able to publish a package, on an account with no second factor, is a live risk to everything downstream of it. No vulnerability feed will ever tell you about this: there is no advisory, no CVSS score and nothing to upgrade to. There is only the shape of the graph.
This is the query a relational schema handles worst: a recursive closure over the dependency table, joined against a GROUP BY … HAVING COUNT(*) = 1 over maintainers, collapsed again by a distinct count. Here it is one traversal and a four-line predicate.
Packages are listed by the maintainer who solely owns them; follow a name to see every application that sits above their work and by what route. Package links: pygments undici has-flag ms util-deprecate balanced-match brace-expansion concat-map