Client logs now show the full request chain behind a package download

Client logs in the Cloudsmith web app now capture format-specific metadata across every package format Cloudsmith supports. This gives you complete visibility into the traffic being served across your workspace, including package metadata fetches across your toolchain, not just direct package downloads.

Format-specific metadata is currently available in client logs in the web app. Log exports will include this data from November 2026.

Example: An npm install

You can now see the full chain that led to a package download, including exactly which version a build pulled. For example, for the following npm install, the initial request results in two additional hops, all recorded and available in client logs:

15:35:31: npm requests metadata for the @csm/e2e2-push-cli package from the native domain (npm.cloudsmith.io):

15:35:31: Cloudsmith resolves the request to version 1.0.0-e69fae5b and returns a 307 redirect response to the download domain (dl.cloudsmith.io):

15:35:32: Cloudsmith serves the 1.6KiB file from dl.cloudsmith.io with a 200 response:

For more information about using client logs, see the Cloudsmith documentation.