> The workaround in many cases would be as simple as pointing your package.json file to GitHub instead of npm.org. Or paying to download it once and then cachin

> The workaround in many cases would be as simple as pointing your package.json file to GitHub instead of npm.org. Or paying to download it once and then caching it in some local NPM proxy. You just described like $1,000 worth of work. If the price of conveniently getting access to code were tarsnap style fractions of a cent then any company that is hiring people wouldn’t care. I can’t seem to copy any more of your response because safari is being funny on my phone but from what I can see the chief complaint among open source maintainers is how challenging it is to get meaningful contributions from the user community in the first places I don’t even think you’d need to change the license on the software, it could still be MIT but instead of being copyright Some Coder In Nebraska it would be copyright NPM. Or not maybe you don’t need the copyright to change, I think the key innovation here is that the distribution network takes the payment directly and pays someone to maintain the project.