Chainguard Libraries for Java provides enhanced security for the Java ecosystem by rebuilding dependencies from Maven Central and other common repositories with the latest patches and comprehensive supply chain protection. This service addresses critical vulnerabilities in the vast Java\/JVM ecosystem that spans hundreds of projects from organizations like the Apache Software Foundation, Eclipse Foundation, and numerous independent maintainers.<\/p>\n
Chainguard Libraries for Java provides access to all open source libraries\ncommonly used. New releases of common libraries or artifacts requested by\ncustomers are added to the growing index by an automated system. The number of\nincluded libraries continues to grow. These artifacts are accessible through the\nChainguard Repository<\/a>,\na single endpoint for package retrieval that supports configurable security\npolicies for both Chainguard-built and upstream packages.<\/p>"},{"title":"Global configuration","link":"https:\/\/edu.chainguard.dev\/chainguard\/libraries\/java\/global-configuration\/","pubDate":"Tue, 25 Mar 2025 08:04:00 +0000","guid":"https:\/\/edu.chainguard.dev\/chainguard\/libraries\/java\/global-configuration\/","description":" Java and JVM library consumption in a large organization is typically managed by\na repository manager. Commonly used repository manager applications are\nCloudsmith<\/a>, Google Artifact Registry<\/a>, JFrog\nArtifactory<\/a>, and Sonatype Nexus\nRepository<\/a>. The\nrepository manager acts as a single point of access for developers and\ndevelopment tools to retrieve the required libraries.<\/p>\n At a high level, adopting the use of Chainguard Libraries consists of the\nfollowing steps:<\/p>\n Additional steps depend on the desired insights and can include the following\noptional measures:<\/p>"},{"title":"Build configuration","link":"https:\/\/edu.chainguard.dev\/chainguard\/libraries\/java\/build-configuration\/","pubDate":"Tue, 25 Mar 2025 08:04:00 +0000","guid":"https:\/\/edu.chainguard.dev\/chainguard\/libraries\/java\/build-configuration\/","description":" The configuration for the use of Chainguard Libraries depends on your build\ntools, continuous integration, and continuous deployment setups<\/p>\n At a high level adopting the use of Chainguard Libraries consists of the\nfollowing steps:<\/p>\n These changes must be performed on all workstations of individual developers and\nother engineers running relevant application builds. They must also be performed\non any build server such as Jenkins, TeamCity, GitHub or other infrastructure\nthat builds the applications or otherwise downloads and uses relevant libraries.<\/p>"},{"title":"Management and maintenance","link":"https:\/\/edu.chainguard.dev\/chainguard\/libraries\/java\/management\/","pubDate":"Tue, 25 Mar 2025 08:04:00 +0000","guid":"https:\/\/edu.chainguard.dev\/chainguard\/libraries\/java\/management\/","description":" Chainguard Libraries for Java operates transparently after completing the global configuration<\/a> and build configuration<\/a>, automatically providing security-enhanced versions of your Maven dependencies. New artifacts and versions are retrieved from Chainguard’s hardened repository when available, while Maven Central and other configured repositories provide fallback access to ensure continuous development workflow without interruption.<\/p>\n The following sections detail optional management, maintenance, and auditing\nsteps on the repository manager and the build tool.<\/p>\n\n
\n