<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chainguard Libraries on</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/</link><description>Recent content in Chainguard Libraries on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 25 Mar 2025 08:04:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/index.xml" rel="self" type="application/rss+xml"/><item><title>Chainguard Libraries overview</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/overview/</link><pubDate>Tue, 25 Mar 2025 08:04:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/overview/</guid><description>Chainguard Libraries provide enhanced security for open source dependencies in the Java, JavaScript, and Python ecosystems, addressing critical supply chain vulnerabilities through automated patching and continuous monitoring. Modern applications rely heavily on libraries from public repositories like Maven Central, npm Registry, and PyPI, but using these repositories introduces supply chain risks that could expose your applications and system to compromise.
Background Open source libraries distributed through public repositories face several security challenges: maintainers may not promptly address vulnerabilities, binary artifacts can be compromised, and the sheer volume of transitive dependencies makes manual security management impractical.</description></item><item><title>Chainguard Libraries access</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/access/</link><pubDate>Tue, 25 Mar 2025 00:08:04 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/access/</guid><description>Chainguard Libraries provide controlled access to security-enhanced Java and Python dependencies through the unified Chainguard platform authentication system. This guide explains how to access (download) Chainguard library artifacts for your organization.
Getting started Prerequisites Ensure you have access to Chainguard Libraries. If you are not a Chainguard user yet, a new Chainguard account must be created and configured for access to Chainguard Libraries. If you are already a Chainguard user, the Chainguard account owner in your organization can grant access to Chainguard Libraries.</description></item><item><title>Chainguard Libraries network requirements</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/network-requirements/</link><pubDate>Wed, 04 Jun 2025 09:30:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/network-requirements/</guid><description>Chainguard Libraries require specific network access to ensure secure delivery of hardened dependencies to your development environment. This guide details the domains and ports needed for authentication, package downloads, and verification tools.
Access for chainctl and other tools For initial configuration with chainctl as well as for verification of downloaded libraries with cosign and other tools, you must allow HTTPS access to the following domains:
dl.enforce.dev for download and update of chainctl issuer.</description></item><item><title>Chainguard Libraries verification</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/verification/</link><pubDate>Thu, 03 Jul 2025 12:00:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/verification/</guid><description>Overview Chainguard&amp;rsquo;s chainctl tool with the command libraries verify verifies that your language ecosystem dependencies come from Chainguard Libraries, providing critical visibility into your software supply chain security. By verifying binary artifacts across your projects and repositories, you can ensure dependencies are sourced from Chainguard&amp;rsquo;s hardened build environment rather than potentially compromised public repositories, identify opportunities to improve security posture, and maintain compliance with supply chain security policies.
Command characteristics:</description></item><item><title>CVE remediation for Chainguard Libraries</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/cve-remediation/</link><pubDate>Thu, 11 Sep 2025 00:00:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/cve-remediation/</guid><description>CVE remediation is a feature in Chainguard Libraries that provides security protection against critical and high CVEs, while medium or low CVEs are not considered. Applications often rely on older versions of libraries, but upstream maintainers may not apply and release patches for those versions. CVE remediation addresses this gap by applying vulnerability fixes from newer releases to older releases, particularly in cases where maintainers are no longer able to support and provide fixes.</description></item><item><title>Vulnerability scanners and Chainguard Libraries</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/scanners/</link><pubDate>Sat, 04 Oct 2025 12:00:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/scanners/</guid><description>Vulnerability scanners enable you to understand the potential security risks from libraries used within your applications.
Chainguard Libraries provides a trusted source for libraries typically downloaded from public repositories. Chainguard Libraries are rebuilt from the upstream open source project code repository content only. This prevents malware without published source code and reduces almost all risk for software supply chain attacks. In addition, some library versions are available with CVE fixes applied.</description></item><item><title>Browsing Chainguard Libraries</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/browse/</link><pubDate>Thu, 03 Jul 2025 14:00:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/browse/</guid><description>Chainguard Libraries includes thousands of libraries and many more individual library versions and artifacts. Through the Chainguard Console, you can browse all available libraries and their versions, and inspect their characteristics before using them in your application development.
Access libraries in the Chainguard Console Log in to the Chainguard Console at https://console.chainguard.dev/.
In the left-hand navigation under Libraries, expand Ecosystems to find links for browsing Chainguard&amp;rsquo;s Java and Python libraries.</description></item><item><title>Chainguard Libraries FAQ</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/faq/</link><pubDate>Tue, 25 Mar 2025 08:04:00 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/libraries/faq/</guid><description>What security issues can Chainguard Libraries prevent? As detailed on the background and introduction pages, Chainguard Libraries are built directly from source in the Chainguard Factory and the resulting binaries are directly provided to you by Chainguard. Chainguard operates the whole supply chain for the package lifecycle as one reliable, secure partner. You can therefore avoid issues from the following software supply chain attack surface points:
Build pipeline Build system Dependency injection Bypass of CI/CD systems Library distribution Library consumption More information about these stages in the software supply chain is available on the Supply chain Levels for Software Artifacts (SLSA) website.</description></item><item><title>How does Chainguard Libraries plug into a developer's workflow?</title><link>https://deploy-preview-3175--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-3175--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><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>