As part of upcoming improvements to our logging pipeline, we’ve made adjustments to our underlying data processing. These changes include the path and uri fields in the web application and the uri field in Client Logs exports.
These fields will now be prefixed with the name of the workspace and the repository.
For example:
/format/package_name/filenameWill change to:
/workspace/repository/format/package_name/filenameIf you are using custom domains configured at the workspace level, only the repository name will be prefixed:
/repository/format/package_name/filenameFor repository custom domains, the path will remain unchanged:
/format/package_name/filenameIf you currently parse the uri field in any automated process, please review your workflows to ensure they will continue working as expected. Note that the exact structure of the URI may change depending on the HTTP request type.
If you have any concerns or questions, contact us for help.
Identify and prioritize new vulnerabilities in your existing artifacts with Cloudsmith’s Continuous Security. Continuous Security runs hourly checks against trusted vulnerability data sources, enabling faster detection and response to newly disclosed threats without the need for manual re-scans…
Packages added to Cloudsmith are scanned for vulnerabilities and malware, and passed through our policy engine. When we identify vulnerable packages, we produce and collate a range of descriptive data to help explain those vulnerabilities. Previously, that data was only available in our legacy web app, and more recently via our API. We've now broug…
The official Cloudsmith extension for Visual Studio Code is here. It brings your package visibility workflow directly into the IDE, allowing you to browse and inspect repositories and packages without switching context…
Client log exports now provide a more comprehensive overview of package delivery. In addition to GET requests, client log exports will include other HTTP request types, including HEAD, POST, and OPTIONS requests. This gives you a full view of package delivery, moving beyond just download tracking to include metadata checks and other repository interactions…
You can now use package license data in Enterprise Policy Management (EPM) to create policies based on a package’s software license. This lets you automatically govern license usage in line with your organization’s policies, giving you direct control over which packages are approved for use in your software supply chain…
Client logs and usage reporting improvements are now generally available in the new web application. These updates give you deeper visibility into package downloads, delivery trends and the repositories or tokens driving your usage…
