Sr. Security Specialist at iteratec // @seemoo alumni // Member of CCC // Crypto means cryptography.
tfr.
| Blog | https://blog.maass.xyz |
| GitHub | https://github.com/malexmave |
| Pixelfed | https://pixel.infosec.exchange/@hacksilon |
| Pronouns | he/him |

Sr. Security Specialist at iteratec // @seemoo alumni // Member of CCC // Crypto means cryptography.
tfr.
| Blog | https://blog.maass.xyz |
| GitHub | https://github.com/malexmave |
| Pixelfed | https://pixel.infosec.exchange/@hacksilon |
| Pronouns | he/him |
@nopatience This is a really cool website, thank you. I have it open in a tab and check it once a day to see if I missed something important.
Do you share the list of sources that you are using for this anywhere?
🧨 Axios only needed to be resolved somewhere in your dependency graph to affect you.
Semver + transitive deps + runtime installs = hidden blast radius.
If you only checked your project’s lockfile, you may still not know.
https://socket.dev/blog/hidden-blast-radius-of-the-axios-compromise #nodejs
@foxbasealpha just FYI: unless you combine it with an external SSD or other storage device, I would recommend skipping the Pi and going for a mini PC with SSD or HDD. Pi‘s with SD cards have a nasty habit of frying the card due to the many write cycles home assistant uses. I have a Beelink PC with Proxmox that is running HA and some other stuff in individual VMs, and this also gives you some more breathing room in terms of CPU and RAM, depending on the specs you get.
In terms of the comparison between Pi‘s, I can’t offer any recommendation as I haven’t tried either.