Polish: Claim + DNS-verify trunk.io for the Trunk publisher on VS Marketplace
Current state
The Trunk publisher on the VS Code Marketplace has the verified-publisher badge (✓) already, but no publisher domain is claimed.
Inspected via the marketplace API on 2026-06-30:
Publisher: Trunk
Extension: Trunk.io (Trunk Code Quality)
Flags: verified ← publisher account verified
Domain: (empty) ← no domain claim
DomainVerified: False ← N/A without a claim
Installs: 214,623
Why this is a stronger ask than for solo maintainers
Trunk is a commercial company (trunk.io), not an individual maintainer. The trust-signal argument is stronger here than for solo OSS authors:
- Commercial company with an obvious domain (
trunk.io)
- The extension does AI-driven code analysis and uploads diffs to Trunk's hosted service
- 214K+ installs
For a commercial publisher with cloud sync, domain verification is a standard expectation, not just optional polish.
How to complete
- Sign in to https://marketplace.visualstudio.com/manage/publishers/Trunk
- Edit publisher profile → set Domain to
https://trunk.io
- Domain verification → Microsoft provides a one-time DNS TXT record
- Add the TXT to
trunk.io DNS (TXT can be removed once verified)
- Click "Verify"
5-minute task on the maintainer side.
Why I'm filing here
Trunk's VS Code extension doesn't have a public GitHub Issues tracker (the extension source isn't open-source on GitHub). Filing this on trunk-io/plugins as the closest visible issue tracker for the Trunk team. If there's a better channel, please redirect — or feel free to close as out-of-scope here and handle internally.
Reference
Filed as part of a publisher-trust audit across the extensions I use. Sibling polish requests at biomejs/biome#10810, foambubble/foam#1674, sourcery-ai/sourcery#481, tomoki1207/vscode-pdfviewer#206, and others.
Thanks for Trunk Code Quality — the "one extension instead of 30" pitch is genuinely useful.
Polish: Claim + DNS-verify
trunk.iofor theTrunkpublisher on VS MarketplaceCurrent state
The
Trunkpublisher on the VS Code Marketplace has the verified-publisher badge (✓) already, but no publisher domain is claimed.Inspected via the marketplace API on 2026-06-30:
Why this is a stronger ask than for solo maintainers
Trunk is a commercial company (trunk.io), not an individual maintainer. The trust-signal argument is stronger here than for solo OSS authors:
trunk.io)For a commercial publisher with cloud sync, domain verification is a standard expectation, not just optional polish.
How to complete
https://trunk.iotrunk.ioDNS (TXT can be removed once verified)5-minute task on the maintainer side.
Why I'm filing here
Trunk's VS Code extension doesn't have a public GitHub Issues tracker (the extension source isn't open-source on GitHub). Filing this on
trunk-io/pluginsas the closest visible issue tracker for the Trunk team. If there's a better channel, please redirect — or feel free to close as out-of-scope here and handle internally.Reference
Filed as part of a publisher-trust audit across the extensions I use. Sibling polish requests at biomejs/biome#10810, foambubble/foam#1674, sourcery-ai/sourcery#481, tomoki1207/vscode-pdfviewer#206, and others.
Thanks for Trunk Code Quality — the "one extension instead of 30" pitch is genuinely useful.