Running actions on your own machine doesn't solve cache poisoning or supply chain attacks, your VM will download compromised npm package or github actions the same way GH runner does.
Version pinning/script disabling makes a compromise slightly less likely, rolling your own package server helps a lot (but who got time to maintain version whitelist).
Honestly the best solution is to have minimum amount of dependencies. You don't need a GH action to ping indexers or generic foreign key library for your backed, hammer one yourself.
That and scope all your keys so the leak won't be as devastating 🤷♀️
Yes but the reality of JavaScript codebases is that you'll typically import hundreds if not thousands of dependencies fairly quickly. Last time I looked at the UI codebase at my job it was sitting at over 40k.
IDK how other people are, but to me solving a problem with a single #include just feels right. Less code to maintain, responsibility is shifted to a dedicated person, obviously much faster.. But also constant anxiety and daily monitoring of security blogs, so I'm trying to cut back
7 Comments
ultimate_worrier@lemmy.dbzer0.com · 9 pts · 97d
Maxxie@piefed.blahaj.zone · 6 pts · 97d
Running actions on your own machine doesn't solve cache poisoning or supply chain attacks, your VM will download compromised npm package or github actions the same way GH runner does.
Version pinning/script disabling makes a compromise slightly less likely, rolling your own package server helps a lot (but who got time to maintain version whitelist).
Honestly the best solution is to have minimum amount of dependencies. You don't need a GH action to ping indexers or generic foreign key library for your backed, hammer one yourself.
That and scope all your keys so the leak won't be as devastating 🤷♀️
lauha@lemmy.world · 3 pts · 97d
Isn't this a sane practice in programming anyway? Just don't go overboard with dependency minimalism.
Piatro@programming.dev · 2 pts · 97d
Yes but the reality of JavaScript codebases is that you'll typically import hundreds if not thousands of dependencies fairly quickly. Last time I looked at the UI codebase at my job it was sitting at over 40k.
lauha@lemmy.world · 2 pts · 97d
That's one of the reasons) why JS development is the shitshow it is.
Maxxie@piefed.blahaj.zone · 1 pts · 97d
IDK how other people are, but to me solving a problem with a single #include just feels right. Less code to maintain, responsibility is shifted to a dedicated person, obviously much faster.. But also constant anxiety and daily monitoring of security blogs, so I'm trying to cut back
onlinepersona@programming.dev · 1 pts · 97d
How do you run it on a local machine?
cockmushroom@reddthat.com · 5 pts · 97d
The 👏 death 👏 of 👏 github 👏 will 👏 never 👏 be 👏 the 👏 death 👏 of 👏 open 👏 source