If you’ve worked with builds and dependencies, you know how quickly small issues can turn into major slowdowns - whether it’s unclear security risks, unexpected build failures, or not knowing if a service is running. With the recent release of Open Source Edge (OSE) for IBM, we have tried to mitigate the above issues and offer better visibility into security, smoother handling of build failures, and an easier way to check service health. 

In my previous blog, I covered the Open Source Edge (OSE) for IBM and its core capabilities. Building on that, let’s see how Open Source Edge (OSE) for IBM continues to improve with features that solve real, everyday challenges for developers. 

As explained above, this update focuses on key improvements: better security visibility, better handling of build failures, and an easier way to check service health. Let’s see each of these features in detail.

Better Security Visibility with CVE Details

Through OSE, users can easily browse and download Python wheel packages. Each package provides rich and useful information including:

•  License details for compliance.
• Upstream and downstream links to provide access to the project’s source code, documentation, and development resources.
•  Wheel status to track availability and readiness. 

This makes OSE a convenient, one-stop platform where developers can quickly evaluate and select the right packages for their needs.

For those who want to understand the guidelines and workflows followed by the PyEco community, the PyEco README provides helpful background and additional context.

Building on these capabilities, OSE now introduces CVE (Common Vulnerabilities and Exposures) details directly within Python wheel packages. This is an important step forward in improving security visibility. The CVE data is refreshed via a scheduled cron job that runs once a week, ensuring that vulnerability information remains up to date.

With CVE information now available alongside existing metadata, developers can:

• Quickly identify known vulnerabilities in packages.
• Assess risks before using a dependency.
• Make more informed and secure decisions during development.

The following screenshots highlight how CVE information is presented within OSE:

When you click a package version, it opens a view showing the Python wheels associated with that version. The Python wheel details pop-up displays the vulnerabilities associated with the package, along with their severity indicators. It also includes key information such as the package license. Additionally, users can click on the wheel file to download it directly.

CVE Detailed View: Provides detailed information about each vulnerability, impact and affected versions, enabling deeper analysis before usage.

Overall, this enhancement makes OSE not just a platform for accessing Python packages, but also a tool that helps developers build safer and more reliable applications.

Status Page for Service Monitoring

A new Status page has been introduced to provide visibility into the health of key services. Users can easily check the status of GHA, OSE, and DevPI from this page.

One of the key advantages of this feature is that it is accessible both without logging into the OSE application and after logging in, enabling quick troubleshooting and transparency at all times.

To explore this feature further, read the full blog here: Stay Updated with the New Status Page on Open Source Edge for IBM

See It for Yourself
👉 Visit Open Source Edge for IBM now

AI Disclosure: Portions of this blog were generated with support from an AI assistant. The author has reviewed, tested, and refined all material to ensure accuracy, completeness, and compliance with IBM’s technical and editorial standards.