Sander Elias
@sanderelias.nl
Tech pioneer who loves to dabble in frontend code.
Thanks for having me.
I had an blast.
When someone has questions, just ask me!
I had an blast.
When someone has questions, just ask me!
November 14, 2025 at 8:07 PM
Thanks for having me.
I had an blast.
When someone has questions, just ask me!
I had an blast.
When someone has questions, just ask me!
Oh, I know how your partner feels...
I married I to that...
I married I to that...
November 1, 2025 at 11:30 AM
Oh, I know how your partner feels...
I married I to that...
I married I to that...
I had a great time there.
If you have any questions, please don't hesitate to ask!
If you have any questions, please don't hesitate to ask!
October 1, 2025 at 7:32 AM
I had a great time there.
If you have any questions, please don't hesitate to ask!
If you have any questions, please don't hesitate to ask!
I had no issues with the site.
And `npm audit` is similar but different.
And `npm audit` is similar but different.
September 16, 2025 at 3:07 PM
I had no issues with the site.
And `npm audit` is similar but different.
And `npm audit` is similar but different.
It would be a little bit safer.
But even if you run inside a container, your code still needs to access your secrets. And when your code has access, so does the malware.
There is no single solution.
BTW, this problem isn't unique to NPM; most software library things have the same problem.
But even if you run inside a container, your code still needs to access your secrets. And when your code has access, so does the malware.
There is no single solution.
BTW, this problem isn't unique to NPM; most software library things have the same problem.
September 16, 2025 at 2:06 PM
It would be a little bit safer.
But even if you run inside a container, your code still needs to access your secrets. And when your code has access, so does the malware.
There is no single solution.
BTW, this problem isn't unique to NPM; most software library things have the same problem.
But even if you run inside a container, your code still needs to access your secrets. And when your code has access, so does the malware.
There is no single solution.
BTW, this problem isn't unique to NPM; most software library things have the same problem.
Yup, that is the one!
Make sure you also have this setting in your CI/CD setup.
Makes the world a bit safer.
Make sure you also have this setting in your CI/CD setup.
Makes the world a bit safer.
September 16, 2025 at 1:34 PM
Yup, that is the one!
Make sure you also have this setting in your CI/CD setup.
Makes the world a bit safer.
Make sure you also have this setting in your CI/CD setup.
Makes the world a bit safer.
Probably, but it's not possible to know for sure.
At least use `npm config` to disable scripts, that will at least prevent a load of issues
I'll look up the exact cmd when back at my desk
At least use `npm config` to disable scripts, that will at least prevent a load of issues
I'll look up the exact cmd when back at my desk
September 16, 2025 at 11:28 AM
Probably, but it's not possible to know for sure.
At least use `npm config` to disable scripts, that will at least prevent a load of issues
I'll look up the exact cmd when back at my desk
At least use `npm config` to disable scripts, that will at least prevent a load of issues
I'll look up the exact cmd when back at my desk