Repo Recon
Map the public reference repository and its declared client or program structure.
Authenticate a project’s artwork, team, website, or off-chain metadata content.
Metaplex Token Metadata attaches descriptive information to a mint. Mutable fields and off-chain resources introduce their own controls.

Metadata is linked to a mint through its account.
An update authority can modify mutable metadata.
A verified creator signature is not a real-world identity check.
A familiar logo or ticker can be copied. Separate the mint’s identity from descriptive metadata, its update authority, and the content served by its URI.
Metaplex currently marks Token Metadata as a supported legacy program. Evaluate its current guidance when designing a new integration.
Walk through the flow. Each step gives you one practical question to investigate.
The mint is the anchor for the asset. A display name or symbol does not uniquely identify it.
Conceptual flow, not a live transaction trace. Use the sources below for implementation details.
Inspect update authority, mutability, and applicable delegated permissions before relying on fixed branding claims.
Look for Metadata account + relevant delegation stateCheck the URI and the storage model separately. An unchanging URI can still serve changing content.
Look for URI + independently reviewed content storageA creator signature attests to an on-chain action. It does not establish nationality, legal identity, or the trustworthiness of the project.
Look for Creator verification fields + external provenanceToken Metadata source and clients. This is a guide to existing integrations, not a recommendation to choose a legacy program for a new design.
Resolving its default branch and pinning one commit.
Read-only · No account connection · No code executionMap the public reference repository and its declared client or program structure.
Authenticate a project’s artwork, team, website, or off-chain metadata content.
Review supported mint controls.
Currently provide a complete Metaplex metadata or creator-provenance audit.
We’ll prefill the target. You review the scope before anything runs.
Live launches require verified holder access.Is the metadata connected to the correct mint?
Who can update the name, symbol, or URI?
Is media storage immutable or merely an ordinary website?
What does a creator verification claim actually prove?