What is the most secure way to handle third-party API keys in client-side VS Code extensions without leaking secrets through telemetry or open-source repos?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What is the most secure way to handle third-party API keys in client-side VS Code extensions without leaking secrets through telemetry or open-source repos?
1 real search · 1 real-search pass
site:code.visualstudio.com/api/references/vscode-api SecretStorage extension telemetry privacy telemetry logger secretsGoogle ↗
OBSERVEDOther / navigational
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
site:code.visualstudio.com/api/references/vscode-api SecretStorage extension telemetry privacy telemetry logger secrets Google ↗
- VS Code SecretStorage API · code.visualstudio.com
- VS Code telemetry guidance · code.visualstudio.com
- TelemetryLogger API · code.visualstudio.com
- VS Code API · code.visualstudio.com
- Extension data storage · code.visualstudio.com
- Common Capabilities · code.visualstudio.com
- Extension runtime security · code.visualstudio.com