Vulnerability scanners and Chainguard Libraries
Details for using vulnerability scanners with Chainguard Libraries.
For the complete documentation index, see llms.txt.
Chainguard Libraries includes thousands of libraries and many more individual library versions and artifacts. In the Chainguard Console, you can browse all available libraries and their versions, and inspect their characteristics before using them in your application development.
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’s Java, JavaScript, and Python libraries.
When you open a specific ecosystem, you’ll see a search input box and a list of libraries. Click any row to open the library detail page.
The list includes the following columns:
setuptools or
Flask-Admin.groupId and artifactId, separated by :. Examples are
org.springframework:spring-core or org.eclipse.jetty:jetty-http.At the bottom of the page, see a total count of available libraries.
The upstream fallback is available for JavaScript, Python, and Java Libraries. The upstream fallback can be enabled or disabled using the chainctl libraries entitlements commands, per ecosystem. Currently, the Chainguard Console can be used to enable, disable, and view the status of the upstream fallback for JavaScript only. At the top of the JavaScript page in the Console, you can see whether upstream fallback is enabled.
Learn more in the Libraries Overview documentation.
When fallback is configured for your organization, you will see all JavaScript packages – including those built by Chainguard and those that are mirrored from upstream npm – in the Console. For a given package, you can see whether it is being served from Chainguard’s rebuilt artifacts or proxied from upstream npm. For Java and Python, you cannot currently view upstream vs. Chainguard-built packages via the Chainguard Console.
Use the Search text input at the top of the libraries list to narrow down the list and to locate a specific library.
Click into a row to view a specific library page.
CVE remediation is available for a subset of Chainguard Libraries for Python and Java. You can view remediated libraries in the Chainguard Console.
In the Python and Java libraries directories, click the Remediated tab to view a list of remediated libraries. Click into a library to see which versions have remediated CVEs.
While viewing the list of remediated versions for a library, click into a version to view more details: which CVEs were remediated, the date that the version was patched, and links to additional resources.
Learn more about browsing remediations in CVE remediation for Chainguard Libraries.
For the JavaScript and Python ecosystems, click the Malware tab to learn how many packages have been blocked by Chainguard due to malware or greyware detection.
The list at the bottom of the page displays all blocked packages, including the package name, blocked version, the date it was blocked on, its MAL ID if available, and signals detected.
To access a library page, click on the row for a specific library in the search results or the initial library list.
On a library’s page, use the search bar at the top to search for specific versions.
The list of library versions includes the following columns:
.jar/.pom for
Java, and .whl/.tar.gz for Python. It is not an aggregation of all
files under a given version.Click on the column titles to change the sort order of the list.
The Chainguard Console provides visibility into your repository configuration and the packages being served. When the upstream fallback is configured for your organization, you will see all packages including those built by Chainguard and those that are mirrored from upstream npm.
Last updated: 2026-07-24 15:09