Back to GrowthDex
Growth idea action plan

VS Code extension SUPPORT.md before review friction

Publish a SUPPORT.md and keep the issue, repository, and license links healthy so the buyer can inspect your operating discipline before the first install prompt asks for trust.

rare tacticfree budget

Why this can grow a startup

VS Code now asks users to confirm trust when they install from a third-party publisher, which means a vague support path costs more than it used to. The runtime security guide tells users to inspect ratings, Q and A, issues, repository, and license before deciding an extension is reliable. The publishing docs tell authors to add SUPPORT.md. Put those together and the lesson is plain: support metadata is not housekeeping. It is part of the trust check that happens before the extension gets a chance to prove itself in the editor.

Company example

VS Code's publishing guide recommends adding SUPPORT.md to the extension root, and the runtime security guide says users should inspect Q and A, issues, repository, license, and publisher responsiveness before installing.

Source and metric

Source: Visual Studio Code Docs: Extension Runtime Security

As of VS Code 1.97, first-time installs from third-party publishers prompt the user to confirm publisher trust.

TrustSupportMarketplacesdeveloper toolssupport surfacepublisher trustissue routing
GrowthDex operator note

When to use it

Use this when Trust, Support, Marketplaces is relevant to developer tools, support surface, publisher trust and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Visual Studio Code Docs: Extension Runtime Security and identify what is directly supported.
  2. Choose one channel context: Trust, Support, Marketplaces.
  3. Define the test around As of VS Code 1.97, first-time installs from third-party publishers prompt the user to confirm publisher trust..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian