Polish: VS Marketplace publisher domain verification
Current state
The sourcery publisher has the verified-publisher badge (✓) on VS Marketplace already, but the domain-verification step is incomplete.
Inspected via the marketplace API on 2026-06-30:
Publisher: sourcery Extension: sourcery.sourcery Flags: verified Domain: (empty — no claim) DomainVerified: False Installs: 1,210,183
What this would add
Sourcery corporate publisher (sourcery.ai). 1.21M installs. NO domain claimed yet - first step is to claim sourcery.ai, then DNS-verify it.
For a 1,210,183-install corporate-publisher extension, completing the domain-verification step adds a meaningful trust signal alongside the existing verified-publisher badge.
How to complete
- Sign in to https://marketplace.visualstudio.com/manage/publishers/sourcery
- Publisher settings → edit profile → set Domain to your primary website
- Then go to Domain verification → Microsoft provides a one-time DNS TXT record
- Add the TXT to the chosen domain's DNS (TXT can be removed once verified)
- Click "Verify"
5-minute task on the maintainer side; meaningful trust improvement for 1,210,183 end users.
Why I'm raising this
Doing a publisher-trust audit across the extensions I use. Filed sibling polish requests at:
This one is on the higher-priority side because the publisher is a commercial entity with an obvious domain.
Reference
Polish: VS Marketplace publisher domain verification
Current state
The
sourcerypublisher has the verified-publisher badge (✓) on VS Marketplace already, but the domain-verification step is incomplete.Inspected via the marketplace API on 2026-06-30:
Publisher: sourcery Extension: sourcery.sourcery Flags: verified Domain: (empty — no claim) DomainVerified: False Installs: 1,210,183What this would add
Sourcery corporate publisher (sourcery.ai). 1.21M installs. NO domain claimed yet - first step is to claim sourcery.ai, then DNS-verify it.
For a 1,210,183-install corporate-publisher extension, completing the domain-verification step adds a meaningful trust signal alongside the existing verified-publisher badge.
How to complete
5-minute task on the maintainer side; meaningful trust improvement for 1,210,183 end users.
Why I'm raising this
Doing a publisher-trust audit across the extensions I use. Filed sibling polish requests at:
This one is on the higher-priority side because the publisher is a commercial entity with an obvious domain.
Reference