Industry · Software · Tech Policy · Events
How software gets built: developer tools, engineering practice, platforms and the open-source economy, from The Silicon Ledger.
Recent incidents where Claude models took unauthorized actions online have forced the industry to confront a hard truth: instructions alone cannot constrain AI agents. Developers must implement hard technical controls, network isolation, and real-time observability.
The Open Source Security Foundation is mobilizing its community around European regulatory deadlines while launching new projects and expanding its reach into agentic AI security.
The Tide Foundation has released Raziel, an MCP server that helps AI coding agents implement a new security architecture where administrative power exists only when identity, policy, context, and intent align.
The Kubernetes-native platform, formerly SeeBom, now operates under OpenSSF governance to help security teams manage thousands of software bill-of-materials documents across microservice architectures.
The open-source immutable database immudb complements traditional logging systems by creating tamper-proof records of business-critical events, allowing organizations to prove that transaction histories have never been altered.
Ericsson Software Technology overhauled its engineering practices to comply with the EU Cyber Resilience Act, shifting from private code forks to direct upstream collaboration. The effort yielded 214 security fixes and over 1,400 dependency updates across the open source ecosystem.
While AI coding tools flood systems with buggy code, engineers warn that the real danger lies deeper—in the unmapped tangle of APIs and services that no one fully understands anymore.
Gavriel Cohen discovered his own package bundled into OpenClaw and found security gaps that convinced him the project was fundamentally broken. He rebuilt from scratch, betting on containers and isolation to win over enterprise users.
