Check a trusted publisher on crates.io or NuGet

Trace an existing package version back to its publishing workflow. These examples use GitHub Actions and the registry's trusted publishing settings.

Before you start

  • Ask a package owner to open the registry settings and get read access to the publishing workflow and an existing successful release.
  • Review the current settings and a completed job. Use any package build checks without starting a new publish.

Data and access

Shared or checked
The package registry checks a workflow identity against its trusted publisher configuration. Use the package and workflow records to trace the published version.
Check separately
Maintainer sign-in, package ownership, and any alternative publishing credentials each have their own access rules.
  1. crates.io

    Open the crate's settings and find its trusted publisher for GitHub Actions. Compare the repository owner, repository, workflow filename and any configured environment with the successful run. If the crate requires trusted publishing, check which release jobs use that method before planning a workflow change.

    Check. The saved publisher and the successful run agree on owner, repository, workflow filename and any configured environment.

  2. NuGet

    On NuGet.org, choose Trusted Publishing from the account menu. Check the repository owner, repository, workflow filename and any GitHub environment on the policy. Confirm that the policy is active, its NuGet owner owns the package, and its scope covers that package and action. A temporarily active policy expires after seven days without a successful publish.

    Check. The policy shows active status with the expected package owner and scope. Verify that the workflow on record matches the policy.

  3. Match the published version

    Find the package's exact version in the registry. Open the workflow run that published it and record the source revision, workflow file, environment if used, and registry version. Check the job output to confirm which publishing method it used.

    Check. The registry version and the workflow’s revision are linked in your record. Mark the authentication method unconfirmed if the run does not show it.

Check your result

Record the registry entry and the matching run. If you can see the current settings but cannot identify how that release authenticated, record the publishing method as unconfirmed.

How to verify your setup

If you get stuck

The job ran but the registry did not accept the publish

Compare the repository, workflow filename and environment against the configured policy. Check the workflow's permission to request an identity token and whether the registry already lists the version. Read the original publishing error before deciding what to change.

Report a problem with this guide

Explore all setup guides →