Chainguard

Show what you know 🥇 Chainguard Courses teach you supply chain security from the ground up. Learn how to: ✅ Secure your agentic engineering ✅ Get started with Chainguard Containers and Libraries ✅ Go from compliance to real security ✅ Customize and make Chainguard your own ✅ Stay ahead of risks Finish a course, earn a badge, and add it to your LinkedIn (all for 🆓!): https://lnkd.in/e-75zCzQ

Every unpatched CVE is a bet that no one exploits it before you fix it. And for teams stuck on older versions of Java, the odds get worse every year you put off patching. (We’re talking 242 new CVEs published daily, up 80% from 2025 👀)  If you're stuck on hard-to-upgrade Java versions, pulling a backported version keeps your application secure while you focus on shipping what’s next. Chainguard Libraries for Java now includes CVE remediation, letting you stay safe while you plan your next major upgrade👇 https://lnkd.in/gyww6tM2/?utm_campaign=li_amer_acq_thought-leadership_tof_corpmarketing&utm_source=linkedin&utm_medium=paid&utm_id=1173027873&hsa_acc=512262371&hsa_cam=1173027873&hsa_grp=809924703&hsa_ad=1508097333&hsa_net=linkedin&hsa_ver=3/

"The companies and public services our communities depend on—from hospitals to water treatment plants to the infrastructure that powers the internet—are at risk." Defending critical infrastructure isn't something any one company can do alone. We’re glad to join OpenAI's call for collective action on cyber defense: https://lnkd.in/gFeKj4Q7

Join us live for Women in Sales: Success Stories at Chainguard, a candid conversation with women building successful careers in sales at Chainguard. Moderated by Katie Kilroy, Chief of Staff to the CEO, the panel brings together Delicia de Jong, Kara Patman, Katie Hathaway, and Tayla Walker to share the experiences, lessons, challenges, and pivotal moments that have shaped their careers. We’ll talk about what success in sales actually looks like, how careers evolve, navigating challenges and opportunities, and the advice they’d give to others building their own path in the field. Whether you’re already in sales, considering a career in it, or simply curious about the people behind Chainguard’s growth, tune in for an honest conversation about careers, confidence, growth, and finding your own version of success. Live on October 15 at 11:00 a.m. PT / 2 p.m. ET via YouTube Live Stream Register for the Event by clicking “notify me” to get a reminder when we go live- https://lnkd.in/gxXHM6if

"Open Source had a great childhood. For two decades, it got to be a kid. It ran around barefoot, gave everything away, trusted strangers, and never once thought about who was watching. It ran the kind of lemonade stand that took IOUs from anyone who wandered up — take what you need, pay me back whenever, no need to leave a name. It was idyllic. It was also, in retrospect, a little feral." 🔮 Dan Lorenc's prediction: by 2030, regulated enterprises will run only on open source that's reachable, patched, and accountable, because they'll be complying with that standard. Read his take on open source's maturation 👇

🏆 We made the list! 🏆 We're thrilled to be named one of Fortune's Best Workplaces, which highlights organizations that foster a positive, inclusive, and engaging culture. We owe it all to our Chainguardians 💜 https://lnkd.in/eqJWmbhS

Here's a peek into one of our favorite Slack channels at Chainguard, #guarddogs 🐶 Happy International Dog Day to everyone's favorite coworkers! 💜

We 💜 you too, Lenny Rachitsky 🫂 Chainguard made Lenny's list of the 100 companies he'd join if he were job hunting today! The Lenny 100 is made up of companies with high talent density, significant upside, and critical problems to solve. And even with 61% headcount growth in the past year, we're *still* growing. 👀 (Join us!) Full list here: https://lnkd.in/gtGfbstd

Chainguard has a blog series called This Shit is Hard, about the unglamorous engineering behind software people can rely on. They asked Sara Kromwijk and me to write about ours: getting AI to prove where a number came from. The short version is that provenance has to survive every tool call, every agent handoff, every computation. If it breaks anywhere, you can't stand behind the number, even when the model got it right. This was a fun one to write, and even more fun to work on every day. Link in comments

How do you safely run code you didn't write and can't review? That's a problem we ran into when patching undisclosed vulnerabilities through Athena. Matt Moore shares what we learned from the coalition and why we had to build a sandbox: https://lnkd.in/dxaZJqMm