Hey everyone, I've been trying to get my OpenClaw setup more secure following the guides on supply chain integrity. I'm really glad the tools have default pinning for the main packages, that makes sense to me.

But I was reading through the docs and a few older threads here, and I think I hit a confusion point 😅. From what I understand, the default pinning (like in the standard docker-compose for the agent) pins the version of the main OpenClaw tool image, right? But it doesn't seem to lock down the dependencies *inside* that image, or any other tools it might pull in during runtime. So those transitive dependencies could change without the main image version changing.

Is that the correct way to think about it? It feels like we're trusting the build process of that container image a lot, which is probably fine, but I want to be sure.

What are you all doing to get a handle on this? Do you generate SBOMs for the images you use and audit those? Or is there a way to pin deeper, maybe at the OS package level inside the container? I'm still wrapping my head around all the layers involved.