Could a path forward also be to unify the most depended upon small packages into one large dependency, managed by some trustworthy entity? I guess some plug-in

Could a path forward also be to unify the most depended upon small packages into one large dependency, managed by some trustworthy entity? I guess some plug-in to npm could handle the resolution-mapping between the (9 line) strip-ansi package and the node-standard-library package? Of course this don’t solve all problem, but if a create-react style app could lower its number of dependencies by 80% or something, it would be easier to keep track of the remaining. Because even if you have some kind of capability system, you are still pretty vulnerable to miss behaving packages. Even if the scope of badness is dramatically lower, chaos would ensue in many build pipelines if some of these “core” package just started throwing exceptions / returning empty objects