You could set up trivy.dev scanning as part of your CI pipeline. Patch until your builds are green again :)
Doesn't seem something worthy of investing my time into.
You know, the thing you need if you're stuck in 2000's eea deployments. Or the thing you need if you're deploying VMs. Or the thing you need if you're deploying containers. "You know*, the thing you need if you give a shit about your product.
Oh wait, what, you're running a live service, connected to public internet? And you somehow think "lol gotcha rust updates are a thing" is an own? Once again, y'all keep tattling on yourselves!! While acting so smug, I (really don't) need some of that ignorant confidence! *Please!!!!* Feel free to link us to your running live services that you apparently can't run CI/CD for. Its totes fine, right?
> It's called CI
So do you have a CI about every single binary (maybe closed source) that you run?
I don't have a CI for bash, cat, ls, stat, ln, bc, grep… I know they are well maintained and get updates.
If I need a CI as a end user… that thing is already obviously garbage.
> Oh wait, what, you're running a live service, connected to public internet? And you somehow think "lol gotcha rust updates are a thing" is an own? Once again, y'all keep tattling on yourselves!! While acting so smug, I (really don't) need some of that ignorant confidence! Please!!!! Feel free to link us to your running live services that you apparently can't run CI/CD for. Its totes fine, right?
Ping me when you are done making random rageful assumptions thanks.
I'm sure all the go/rust binaries/docker containers out there have sensible paths to keep them up to date, right?