☀️ ‘Tis the sea-son! 🌊
We’re excited to announce our Series Sea (C) round led by @Redpoint, @lightspeedvp, and @IVP. Are you squidding me?! 🤯🐙
We’ve achieved so much in our 2.5+ year journey so far:
🤝 Customers: Partnered with the world’s leading enterprise, security, and technology companies like @anduriltech, @Appian, @Checkmarx, @HPE, @SnowflakeDB, @wiz_io, & more to lock down supply chains everywhere with Chainguard Images!
💜 Doubled the size of our Chainguardian team - check our our careers page to join in on the fun.
🖼️ Images: Built an expansive inventory of secure container images that continues growing with our new Chainguard AI Images, a suite of CPU and GPU-enabled images, including PyTorch, Conda, and Kafka!
We know we would not be here without our investors, customers, employees, and community supporters for helping us get to this milestone. Cheers to a bright future ahead as we continue to work together to be the safe source for open source. 💜
Hear from our Sea-E-O, @lorenc_dan: https://t.co/7aCnDeznXM
🔐 We're excited to announce the Chainguard Trust Center, a dedicated platform where we proactively share security, compliance, and privacy information with our users and customers! 🔐
Get the lowdown on all the resources, and check it out: https://t.co/6cSOyIF5vE
I am impressed by the progress made by my friends at @chainguard_dev, who started a few years ago with the idea that 'distroless images are okay; let's make them great.' The recent adoption of wolfi by @IstioMesh marks a significant milestone in the development of 'What is Distroless? Oh, you meant Wofi!'
👏 @SnowflakeDB builds a secure foundation for their Data Cloud with Chainguard! Here's how they:
✅ Streamline vulnerability management
💯 Achieved #FedRAMP High for container security
🚀 Allowed teams to focus on innovation
See the transformation: https://t.co/xzioXGjuSY
🛑 CVEs slow down developers in a variety of ways, some more visible than others.
See some of the biggest problems they cause, and how Chainguard Images helps mitigate those issues, in this blog from Chainguard Labs' John Speed Meyers: https://t.co/EvOmSbgq4C
🌠🌈 Join us for our next Learning Labs to learn:
💀 What's at stake if you have vulns in your images
🐳 How to migrate a Dockerfile multi-stage build for a Java app to use JDK & JRE Chainguard Images
☕ Debugging a containerized Java app
https://t.co/gumgui83qx
Having a blast at the @chainguard_dev booth at #KubeconEU.
Stop by for good vibes & to eliminate the CVEs plaguing your software supply chain.
📍H28
Chainguard Developer Images are now available on Docker Hub! 🐳+🐙=🔐⛓
We're thrilled to announce that Chainguard has now become a Docker Verified Publisher! Learn about our partnership, and our mission to continue to be the safe source for open source: https://t.co/14UnyHhmEy
🚀 New episode of Ship It!
We're back! @rothgar & @autumn808 talk to @ImJasonH all about how @chainguard_dev builds hundreds of containers without a single Dockerfile
🎧 https://t.co/ksoaqjk2LA
updated Resonate's Dockerfile to use @chainguard_dev rather than Docker's official Go image.
Resonate (docker): 848MB
Resonate (chainguard): 35.3MB
A 96% image size reduction and 0 CVEs!? 👀
🚀 Announcing our $61 million Series B Round🚀
🔮The future is clear: if you adopt open source software you are responsible for securing it.
🔐Our mission is to be *the safe source for open source* to build right, safe & fast.
💜TY for all the support!💜
https://t.co/qxgBwdktGH
From a customer 🫶 "just wanted to say than you to you guys for the blog article covering the policy to test for the deprecated K8s repo. I took advantage of this, added it in and it threw up something we missed" https://t.co/elC0XKjgUs
Coming very soon: Go server production images will use @chainguard_dev base Wolfi images. Goodbye and thank you for all the fish distroless, you did a good job.
A big problem with VEX (and SBOM) adoption is a lack of tooling. So we fixed that today!
We've announced a new spec called OpenVEX.
https://t.co/FqsD9Yq761
We issue OpenVEX statements for all @chainguard_dev images today.
Everything is available at https://t.co/MlWs0NMibo
NEW: @ImJasonH details his journey finding, reporting & working with @github to resolve an information leak bug in GitHub's Container Registry (GHCR).
Full details here: https://t.co/Xhs1dmhr9p