fix: harden dashboard privacy, accuracy, and accessibility - #28
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Hardens the dashboard after the complete code, security, dependency, accessibility, packaging, repository, and public-presentation audit. The change removes persisted account snapshots and an unrelated API request, makes plan references verifiable, tightens the webview boundary, improves WCAG behavior, clears the current dependency advisories, and refreshes the GitHub-facing project presentation.
No linked issue.
Changes
/pricingAPI request and show account limits only for the current planfast-uriandundicitransitively through npm and pin CI to.nvmrcVerification
npm run preflightpassesnpm cisucceeds with Node 22.17.0Privacy
The webview no longer persists usage windows, plan data, timestamps, errors, or PAYG credit through
vscode.setState. Only the non-sensitive collapsed preference remains. The extension-host state stays in memory and API keys remain exclusively in VS CodeSecretStorage.The refreshed screenshot is rendered from the real compiled webview with synthetic values. It contains no API key, account identifier, live payload, or account history.
Notes
chutes.aiallowlist; there is no new background network endpoint..github/social-preview.pngis ready for the repository Social preview setting. Applying it remains an owner-side GitHub UI step because the connected Chrome session currently blocks local file uploads.