Re:Today’s JavaScript trash fire and pile on
by tracker1 on Monday November 26, 2018 @05:53PM
(#18537602)
Maybe it could come down to requiring npm modules be accessible on a publicly accessible git repository with enough instructions in the package to build that package's output. Exceptions would be the more custom/large packages than the rule. Binary packages would of course also need some exceptions.
There could be a concept of "trusted" packages. That have had at least a review step. So either your package is trivial and easily automated or difficult with manual review. Where the costs are absorbed is the thing.
In the end, I do feel that anything that's being published publicly should have publicly available source, and that the build should be repeatable at the least... that wouldn't prevent such a thing (if it was checked into git), but would at least make it harder to hide.
There could be a concept of "trusted" packages. That have had at least a review step. So either your package is trivial and easily automated or difficult with manual review. Where the costs are absorbed is the thing.
In the end, I do feel that anything that's being published publicly should have publicly available source, and that the build should be repeatable at the least... that wouldn't prevent such a thing (if it was checked into git), but would at least make it harder to hide.