Yeah. I Agree with you. Also been thinking about a similar concept for a while. For the negative effects some have mentioned, one could also argue the possibil

Yeah. I Agree with you. Also been thinking about a similar concept for a while. For the negative effects some have mentioned, one could also argue the possibility of a positive effect to make things more open and result in better quality / funded / open projects. As an idea an addition to this could be a community trust score where users also get to vote on a few aspects of a project, like ‘is it well maintained?’, ‘do you understand changes in version updates?’ etc. maybe bad examples, but a few simple metrics which can give a project a good or bad rep based on what the maintainers does as presented by the community - not just nit-picked twitter quotes. Yes, these will need to be crafted carefully so that maintainer cannot game them but the result could be projects getting paid well for doing things that builds trust and makes the project more accessible. Of course I could just look at the PR history and issues etc before I use a new package, but I would trust community feedback more than my 30 min deep dive. Today we only have very vague metrics like npm popularity or github stars, which is very hard to accurately judge what package to choose or not.