<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recommended Practices on</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/tags/recommended-practices/</link><description>Recent content in Recommended Practices on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Sat, 02 Aug 2025 16:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/tags/recommended-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>How does Chainguard Libraries help developers?</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/how-libraries-help-developers/</link><pubDate>Sat, 02 Aug 2025 16:00:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/how-libraries-help-developers/</guid><description>Transcript Interviewer: So how does Chainguard Libraries help developers?
Dustin Kirkland: Yeah, so building off of that Chainguard Factory, we&amp;rsquo;ve actually repurposed all of that automation to not just build packages and containers, but actually fetch libraries directly from their upstream source and recompile those Java binaries—JARs—and those Python binaries—wheels—in a new format, or in the same format rather, but totally bootstrapped from source. The fact that we can rebuild those libraries means that we can actually patch them if necessary.</description></item></channel></rss>