<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integration on</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/tags/integration/</link><description>Recent content in Integration 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-3174--ornate-narwhal-088216.netlify.app/tags/integration/index.xml" rel="self" type="application/rss+xml"/><item><title>How does Chainguard Libraries plug into a developer's workflow?</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/libraries/how-libraries-plug-into-workflow/</link><pubDate>Sat, 02 Aug 2025 16:00:00 +0000</pubDate><guid>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/libraries/how-libraries-plug-into-workflow/</guid><description>Transcript Interviewer: So Dustin, how does Libraries actually plug into a developer workflow?
Dustin Kirkland: Yeah, so I used the word &amp;ldquo;hydrate&amp;rdquo; earlier. We hydrate typically a JFrog Artifactory or a Cloudsmith—we hydrate that registry of artifacts with Chainguard securely built artifacts. And we produce this constant flow of tens of thousands of those library version tuples into that environment. And our customers can come to us and get a license for our entire Java ecosystem or our entire Python ecosystem.</description></item></channel></rss>