Adopt keytrace

[patak-cat]

Describe the feature

As we connect with more services (from npmjs.com, atproto, to github.com, mastodon, etc) we need a way to link these services identities into a single User entity. Keytrace allows us to do exactly that:

One identity, many proofs.
Keytrace links your atproto handle to the accounts you already own — GitHub, DNS, npm, Mastodon, PGP — with signed, portable proofs. You be you, everywhere.

Adopting Keytrace will simplify surfacing of Project/User data in npmx.

To start with, we could implement a profile for each domain that shows the atproto avatar / banner / display name / description and a list of linked accounts from keytrace. Basically implementing a keytrace visualizer in npmx. So for npmx.dev/zeu.dev we should see her linked accounts.

Second step is to allow to link accounts directly from npmx. We can do that in another issue, too. Creating this issue to kick start the process of adopting keytrace and have a place to discuss about it in GitHub.

Additional information

• Would you be willing to help implement this feature?

Final checks

• Read the contribution guide.
• Check existing issues.

[BittuBarnwal7479]

From my understanding, the goal here is to represent a single developer identity (via Keytrace) and surface their linked accounts (GitHub, npm, Mastodon, etc.) in one unified profile.

For an initial iteration, I’m thinking of:

• add a mock server route to simulate Keytrace data
• create a simple profile page (e.g., /[domain]) showing avatar, name, description
• display linked accounts in a clean, read-only UI

I’ll keep the structure modular so it can evolve later with real Keytrace integration and additional features.

Does this direction align with what you had in mind for the initial step?

[patak-cat]

They pointed out to me that we already have a profile page at https://npmx.dev/profile/{domain}, so we can start working there directly. The rest sounds good to me, but you'll probably work with others on the code side so I'll let them check this (or your PR directly). Thanks for jumping in to help!

[BittuBarnwal7479]

They pointed out to me that we already have a profile page at https://npmx.dev/profile/{domain}, so we can start working there directly. The rest sounds good to me, but you'll probably work with others on the code side so I'll let them check this (or your PR directly). Thanks for jumping in to help!

Got it, thanks for pointing that out!

[BittuBarnwal7479]

20260421-2029-49.2837562.mp4

Hii @patak-cat , I’ve shared a short video of a POC for the Keytrace visualizer on /profile/{domain}.

In brief, it adds:

• a unified profile view (avatar, name, description)
• a “Linked Accounts” section with multiple identities (mocked data, read-only)

Would love quick feedback on whether this direction and structure make sense before I proceed further.

Thanks!

[patak-cat]

I think it does, it would be good to connect with real data. I'll let others review and guide on implementation/design once you send the PR.