Single source of truth for planned work. Tiered by execution priority. Completion history lives in git history and
CHANGELOG.md; consolidated research conclusions live inRESEARCH.md. Legacy planning passes are reference-only underdocs/archive/.Roadmap version: Round 99 - Greasy Fork handoff cleanup hardening 2026-06-11. Shipped baseline: v3.11.0 (2026-05-19, tag pushed).
mainhas additional unreleased hardening, TS promotion, Firefox validation, and release-trust commits through 2026-06-11. Test suite: 1582 Vitest cases green;npm audit --audit-level=high --omit=optionalclean; 28/28 TS-promoted runtime entries; 0 mirrored; 0 divergent. Source floor: 400+ external URLs across Rounds 1-40. Every Now/Next item carries source IDs from the Appendix.Last researched: Round 92 - 2026-06-07.
Tampermonkey was briefly removed from CWS in July 2025 [S01] but returned and now sits at v5.5.0 with 12M users — the dominant incumbent. Violentmonkey remains MV2-only (v2.41.0, actively developed) but permanently blocked on Chrome 133+ (MV2 fully removed in Chrome 139) [S02, S03]. ScriptCat (4.5K stars) is MV3-native but niche [S04]. New entrants include Tweeks (YC W25, AI-native) and lightweight MV3 managers (OrangeMonkey, Vanilla Pudding, BareScript). Greasemonkey and FireMonkey remain Firefox-only MV2 [S05, S06].
ScriptVault is the only MV3-native, open-source, full-featured userscript manager with zero telemetry on the Chrome Web Store. Tampermonkey's return narrows the MV3 exclusivity window, but its closed-source and freemium model remain trust liabilities. The roadmap prioritises differentiation: ship Firefox AMO, land Edge, close GM API parity gaps, and capitalize on trust advantages (Ed25519 signing, AST analysis, update review, MIT license).
| Tier | Meaning | Timeframe |
|---|---|---|
| Now | Active queue. Ship in v3.12.0. | Days to weeks |
| Next | Planned for v3.13.0-v3.14.0 after Now clears. | Weeks to months |
| Later | Validated direction, not yet scheduled. | Months to quarters |
| Under Consideration | Promising but needs more research or user signal. | Unscheduled |
| Rejected | Evaluated and declined, with reasoning. | N/A |
Priority labels within tiers: P0 safety/security/data-loss, P1 core workflow gaps, P2 polish, P3 nice-to-have.
(All Now-tier items are credential/compliance blocked — see Roadmap_Blocked.md.)
Findings from a six-agent deep audit (workbench redesign UI, typed action
dispatch, recent security commits, UserCSS/language service, locale/controllers,
secondary surfaces). ~30 confirmed items were fixed across commits c62c19e
(UserCSS engine), c02e26d (source maps), c13f7f8 (UserCSS UI + LSP),
780c837 (error-log URL retention), b419671 (workbench UI), e230d54
(secondary surfaces), and 259536b (controllers + a11y gate). The items below
are lower-priority findings deferred for a later pass.
-
P3 — Full
parseUserCSSruns on every editor keystroke for UserCSS drafts Why:META_REGEXover the whole document plus directive parsing/validation on the main thread causes jank on large styles; reuse the parse fromscheduleUserCssPreviewRefreshor debounce. Where:pages/dashboard.js:13260-13269wired to the editor change event. -
P3 — Editor open logs an
insertBeforeNotFoundError (pre-existing) Why:npm run smoke:editorreports one console error on editor open — "Failed to execute 'insertBefore' on 'Node': the node before which the new node is to be inserted is not a child of this node." The editor still works (overlay, code pane, all 14 controls, close), but a DOM insertion path targets a stale/detached reference. Present in the v3.20.0 workbench redesign before the 2026-07-15 audit; trace which render path (likely a tab/toolbar or What's New insertion) holds the stale node. Where:pages/dashboard.jseditor-open render path. -
P3 — MV3 SW-death leaves orphaned UserCSS preview/registered-tab maps Why:
_registeredTabs/_draftPreviewTabsare in-memory; if the worker is killed between injection and a later disable/clear,removeCSShas no record and stale CSS persists until navigation. Persist tab→css bookkeeping. Where:src/modules/userstyles.ts:169-170.
Findings from a six-agent deep audit (correctness, security, cloud-sync/storage,
background core, dashboard UX, dashboard modules, non-dashboard UI). The P0/P1
data-safety and background-hardening items were fixed in commits 17f45bf
(sync data-safety + restrict-to-site scope expansion) and e233c94 (update
lock + SRI @resource + scam-detector precision) — do NOT re-open those. The
items below are the remaining unfixed findings.
- Authoritative source is
src/**(TypeScript).background.js,background.core.js,modules/*.js, andbg/*.jsare GENERATED. The live service-worker logic lives insrc/background/core.ts(a ~13k-line bridge); the focused modules undersrc/background/(e.g.registration.ts,update-checker.ts,resource-loader.ts) are EXTRACTION TARGETS that are NOT wired into the runtime — editing them alone changes nothing at runtime. Grep the generatedbackground.jsfor a symbol to confirm which copy is live before editing; usually you must fix BOTHcore.ts(runtime) and the matching extraction module (drift-cleanliness). The@matchReDoS and restrict-to-site fixes both had to touch two copies for this reason. - After any
src/**edit:npm run ts-runtime:generate→npm run build:bg→npm run typecheck→ focusednpx vitest run <files>→ thennpm run checkbefore committing. Never edit generated artifacts by hand. pages/dashboard.jsis plain JS (no build step) and is LF-pinned. Edit with the Edit tool only — PowerShellSet-Contentrewrites CRLF and breaks the\n-literal source-pin tests (support-snapshot-redaction). Many dashboard styles are duplicated between inlinepages/dashboard.html<style>andpages/dashboard.css— check both.- Theme tokens: the 4 themes (dark/light/catppuccin/oled) are defined in
pages/theme-tokens.cssand the dashboard theme blocks. Prefer semantic tokens over raw hex; verify every change in all four modes. - Add a regression test for every fix (static source-pin at minimum; functional where a harness exists). Commit in logical batches with conventional messages; no AI authorship in commits.
- UC-1. Safari via Native App Container [S40, S41] — Safari lacks
userScriptsAPI. Requires separate Swift project. Reconsider when user demand justifies it. - UC-2. Script Marketplace [S42] — ScriptVault is a manager, not a platform. GreasyFork integration serves the same need.
- UC-3. AI-Assisted Script Editing [S43] — Must be opt-in, local-first. Reconsider when on-device LLMs are practical.
- UC-4. Collaborative/Team Sharing — Small user base. Existing sync covers the 90% case.
- R-1. WXT Migration [S45] — Conflicts with concatenated service worker architecture. Revisit only if codebase moves to multi-file workers.
- R-2. GM3 API Compatibility [S05] — Synchronous APIs conflict with MV3 isolation. TM/VM have moved on.
- R-3. Safari via Polyfill [S40] — Safari lacks
userScriptsAPI. A polyfill cannot bridge this. - R-4. Chrome Sync Provider [S46] — 100KB quota unsuitable for scripts. Seven other providers exist.
- R-5. Built-in Ad Blocking — uBlock Origin's domain.
@webRequestDNR rules cover per-script blocking.
| Cycle | Angle | Local evidence | External signal | Roadmap changes |
|---|---|---|---|---|
| 45 | Setup/onboarding reliability | pages/dashboard.js, pages/popup.js, src/background/registration.ts, README.md support matrix |
Chrome 138+ per-extension Allow User Scripts; Firefox MV3 optional-only userScripts; user-script registrations are cleared on extension update [S48, S74] |
Added N-7 setup doctor and rehydration audit |
| 46 | Developer workflow | Monaco editor, generated GM typings, install provenance, local-save receipts | Tampermonkey external-editor FAQ, Tampermonkey Editors vscode.dev extension, current user complaints about copy-save-reload loops [S77, S78, S79] | Promoted local file/watch work into X-8 |
| 47 | Distribution and publishing | Greasy Fork/OpenUserJS discovery and install provenance in dashboard/install UI | Greasy Fork documents read-only API plus prefilled update form requiring user session cookie [S76] | Added X-9 and corrected L-10 from direct API to publish handoff |
| 48 | Implementation decomposition | pages/dashboard.js editor save/install paths, pages/dashboard.html editor toolbar, src/background/core.ts, docs/release-runbook.md, trust receipt tests |
Chrome File System Access user-gesture/support constraints, Greasy Fork prefill form rules, Chrome/Firefox userScripts update clearing, CWS remote-code policy [S47, S74, S75, S76, S81] | Added N-8 and expanded X-8/X-9 into implementation slices |
| 49 | Compliant background execution architecture | src/background/background-runner*.ts, src/background/background-wrapper.ts, offscreen.js, scripts/check-cws-remote-code.mjs, docs/background-scripts-design.md, docs/cws-remote-code-compliance.md |
Chrome offscreen limits, remote-hosted-code sandbox guidance, ScriptCat background/cron docs [S82, S83, S84] | Expanded X-2 with sandbox-runner candidate, rejected alternatives, and prototype acceptance gates |
| 50 | SPA navigation support | src/background/wrapper-builder.ts, src/background/registration.ts, content.js, tests/wrapper-dom-security.test.js, tests/match-top-39-11.test.js, README/dashboard examples |
Navigation API route events, same-origin scope, and extension webNavigation permission tradeoffs [S85, S86, S87, S88] |
Expanded X-3 from feature note into implementation-ready URL-change contract and verification gates |
| 51 | Local-save trust receipts | pages/dashboard.js, src/background/core.ts, src/background/trust-receipt.ts, src/types/messages.ts, src/types/script.ts, src/modules/sync-easycloud.ts, tests/trust-receipt*.test.js, tests/install-source.test.js, tests/support-snapshot-redaction.test.js, tests/reregister-script.test.js |
File System Access user-gesture/handle-storage limits and CWS user-data/privacy disclosure expectations [S75, S81, S89, S90] | Expanded N-8 with local-source override, autosave coalescing, export/sync redaction, and receipt-operation test gates |
| 52 | Developer workspace/local file binding | pages/dashboard.js, pages/dashboard.html, pages/dashboard.css, src/types/script.ts, src/background/core.ts, src/background/import-export.ts, src/background/cloud-sync.ts, src/modules/sync-easycloud.ts, src/storage/script-db.ts, cloud-sync/export tests |
File System Access stored-handle, permission-persistence, user-gesture, secure-context, and CWS user-data disclosure constraints [S81, S89, S90, S91, S92] | Expanded X-8 with local-only binding store, permission-state UI, refresh-only first release, and export/sync redaction gates |
| 53 | Setup rehydration evidence | src/background/core.ts, background.core.js, background.js, src/types/messages.ts, tests/local-health-report.test.js, dashboard support snapshot export |
Chrome userScripts docs, Chrome 138+ Allow User Scripts, Firefox optional-only userScripts, and update-time registration clearing [S47, S48, S74] |
Implemented aggregate last-registration-sweep evidence in local health reports and support snapshots |
| 54 | Local-save receipt implementation | pages/dashboard.js, src/background/core.ts, src/background/trust-receipt.ts, src/types/messages.ts, src/types/script.ts, tests/trust-receipt.test.js, tests/local-save-trust-receipt.test.js |
CWS user-data disclosure and File System Access user-gesture/stored-handle constraints [S81, S89, S91] | Shipped explicit local editor receipt payloads and metadata-fallback suppression for manual saves/autosaves |
| 55 | Autosave receipt coalescing | pages/dashboard.js, src/background/core.ts, src/types/messages.ts, tests/local-save-trust-receipt.test.js, tests/reregister-script.test.js |
CWS local-storage disclosure plus File System Access handle permission recheck and persistent-permission behavior [S81, S89, S91] | Added ephemeral autosave coalescing keys, in-memory rollback-history reuse, and reregister/export-safety source guards |
| 56 | Local workspace binding store | src/storage/idb.ts, src/storage/script-db.ts, src/modules/storage.ts, src/background/core.ts, modules/storage.js, tests/storage.test.js, export/sync/support tests |
File handles are serializable to IndexedDB; permission must be rechecked with queryPermission()/requestPermission(); local sensitive data remains disclosure-relevant [S81, S89, S91] |
Added local-only binding storage plus JSON export, CloudSync, EasyCloud, and support-snapshot redaction fixtures |
| 57 | Dashboard local file binding | pages/dashboard.html, pages/dashboard.js, tests/local-workspace-dashboard.test.js |
File picker support must be feature-detected and invoked from a user gesture; stored handles require permission-state rechecks; local sensitive data still needs clear disclosure [S81, S89, S91] | Added the feature-detected Bind File control, local IndexedDB handle persistence, permission summary chip, and no-save/no-code binding tests |
| 58 | Local file refresh review | pages/dashboard.html, pages/dashboard.js, tests/local-workspace-dashboard.test.js |
Stored handles may need requestPermission() from a user gesture before reads; local files should be reviewed before applying executable code [S81, S89, S91] |
Added Refresh File and Unbind, review-diff apply, permission reconnect/error summaries, no-change handling, and local-file receipt tests |
| 59 | Deep audit security | src/background/wrapper-builder.ts, src/background/core.ts, generated runtime artifacts, tests/wrapper-dom-security.test.js, docs/research-deep-audit-2026-06-06.md |
Local audit found srcdoc bypass in GM_addElement; iframe srcdoc is raw HTML rather than a normal URL attribute |
Blocked srcdoc for direct attrs and sanitized innerHTML, regenerated runtime artifacts, and pinned the bypass regression |
| 60 | Crontab execution isolation | src/background/core.ts, generated runtime artifacts, tests/crontab-next-fire.test.js, docs/research-deep-audit-2026-06-06.md |
Local audit found scheduled scripts running through chrome.scripting.executeScript in ISOLATED world, which can expose extension APIs to userscript code |
Moved scheduled execution to chrome.userScripts.execute in USER_SCRIPT world with a MAIN-world fallback only, removed the scheduled new Function path, and pinned the isolation regression |
| 61 | PublicAPI internal-host parity | src/modules/public-api.ts, modules/public-api.js, background.js, tests/public-api.test.js, tests/source-hardening-parity.test.js |
Local audit found PublicAPI's private internal-host copy missing .localhost, TEST-NET, benchmarking, Class E, and IPv4-mapped IPv6 hex cases already enforced by InternalHostGuard |
Reused the canonical isInternalHost guard for trusted origins, web install URLs, and webhook URLs, regenerated runtime artifacts, and pinned behavior/source parity regressions |
| 62 | S3 settings validation | src/config/settings-schema.json, pages/dashboard.html, pages/dashboard.js, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
WCAG 2.1 SC 3.3.1 error identification, MDN constraint validation, and aria-invalid guidance still favor field-specific text errors and custom validity [S07, S08] |
Added S3 endpoint/region/bucket/object-key validation metadata, native hints, accessible error nodes, blur hooks, and focused a11y/schema coverage |
| 63 | Sync credential validation | src/config/settings-schema.json, pages/dashboard.html, pages/dashboard.js, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
WCAG 2.1 SC 3.3.1, MDN constraint validation, and MDN aria-invalid guidance still support custom validity plus field-specific error messages [S07, S08] |
Added WebDAV, sync passphrase, and S3 credential validation metadata, error nodes, native length limits, blur hooks, and an encryption toggle guard |
| 64 | Editor select validation | src/config/settings-schema.json, pages/dashboard.html, pages/dashboard.js, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
MDN documents HTMLSelectElement.setCustomValidity() and option values as the select contract; WCAG error identification still requires text errors for invalid choices [S07, S08] |
Added validation metadata, error nodes, and save-blocking allowed-option checks for editor font size, indentation width, and tab size |
| 65 | Interval select validation | pages/dashboard.html, pages/dashboard.js, src/config/settings-schema.json, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
MDN select option values plus HTMLSelectElement.setCustomValidity() support the same allowed-option validation contract [S07, S08] |
Added validation metadata/error nodes for update check, notification delay, and externals intervals; preserved 0/"Never" with nullish fallbacks and validator conversion |
| 66 | Security select validation | pages/dashboard.html, pages/dashboard.js, src/config/settings-schema.json, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
MDN select option values plus HTMLSelectElement.setCustomValidity() support the same allowed-option validation contract, and WCAG error identification expects text feedback for invalid choices [S07, S08] |
Added validation metadata, error nodes, and save-blocking allowed-option checks for content script API, sandbox mode, CSP modification mode, and HTTP header modification mode |
| 67 | Action behavior select validation | pages/dashboard.html, pages/dashboard.js, src/config/settings-schema.json, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
MDN select option values plus HTMLSelectElement.setCustomValidity() support the same allowed-option validation contract, and WCAG error identification expects text feedback for invalid choices [S07, S08] |
Added validation metadata, error nodes, and save-blocking allowed-option checks for default tab type, local file, cookie, communication, SRI, include, @connect, incognito, page filter, block severity, strict mode, and top-level await selects |
| 68 | Remaining select validation | pages/dashboard.html, pages/dashboard.js, src/config/settings-schema.json, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
MDN select option values plus HTMLSelectElement.setCustomValidity() support the same allowed-option validation contract, and WCAG error identification expects text feedback for invalid choices [S07, S08] |
Added validation metadata, error nodes, and save-blocking allowed-option checks for all remaining schema-backed selects; popup columns now validates before numeric conversion |
| 69 | Custom CSS validation | pages/dashboard.html, pages/dashboard.js, src/config/settings-schema.json, scripts/check-settings-schema.mjs, tests/dashboard-a11y.test.js |
WCAG error identification and MDN constraint validation support text errors, native length constraints, and custom validity for malformed free-form text [S07, S08] | Added validation metadata, maxlength, accessible error text, and save-blocking validation for custom CSS; whitespace is preserved while unsafe control characters and overlarge CSS are rejected |
| 70 | Settings validation acceptance gate | scripts/check-settings-schema.mjs, tests/settings-schema.test.js, src/config/settings-schema.json, pages/dashboard.html, pages/dashboard.js |
WCAG error identification and MDN constraint validation still require user-facing errors for malformed input controls [S07, S08] | Added the durable dashboard-backed validation-metadata requirement and closed N-1 after the repository schema passed it |
| 71 | Guarded GM.fetch | src/background/core.ts, src/background/wrapper-builder.ts, background.core.js, background.js, scripts/generate-gm-types.mjs, lib/scriptvault.d.ts, tests/gm-namespace-parity.test.js, tests/gm-types.test.js, docs/gm-namespace-parity.md |
Tampermonkey/Violentmonkey GM API parity still depends on promise-style network helpers, but ScriptVault must keep network access behind GM_xmlhttpRequest policy [S10, S11, S12] |
Added GM.fetch/GM_fetch over the existing XHR bridge, pinned that no background GM_fetch action exists, and closed N-2 |
| 72 | SPA URL-change proof | src/background/core.ts, src/background/wrapper-builder.ts, generated runtime artifacts, tests/urlchange-wrapper.test.js, README.md |
Navigation API route events plus history/popstate/hashchange fallbacks remain the least-permission page-level path for SPA userscript reruns [S85, S86, S87, S88] | Added a shared URL-change scheduler, microtask/frame rechecks, duplicate suppression, jsdom coverage, and README author examples for window.onurlchange |
| 73 | Monaco package guard | scripts/check-monaco-package-contract.mjs, tests/monaco-package-contract.test.js, package.json, docs/monaco-esm-migration-plan.md |
Monaco AMD remains deprecated, but the current v3.12 packaging contract must stay local and Firefox-safe until the ESM bundle is deliberately switched [S17, S24] | Added a static gate for local AMD Chromium packaging, remote/CDN sandbox rejection, Firefox Monaco exclusion, npm-check wiring, and plan drift |
| 74 | Monaco ESM prototype | src/editor/monaco-esm-entry.ts, esbuild.config.mjs, scripts/check-monaco-esm-prototype.mjs, tests/monaco-esm-build.test.js, docs/audit/monaco-esm-prototype-2026-06-06.json |
Monaco ESM needs a local bundled editor plus file-backed workers before the sandbox can leave AMD [S17, S24] | Added an ignored lib/monaco-esm/ prototype build, deterministic worker outputs, font loader handling, post-build evidence checks, and size/layout evidence |
| 75 | Monaco ESM size budget | scripts/check-monaco-esm-prototype.mjs, tests/monaco-esm-prototype-check.test.js, docs/audit/monaco-esm-prototype-2026-06-06.json, docs/monaco-esm-migration-plan.md |
The full JavaScript/TypeScript worker preserves userscript language features, but package growth must be explicit before switching from AMD [S17, S24] | Selected the full-worker Chromium strategy, added total/compressed/per-file budgets, recorded gzip evidence, and pinned budget regressions |
| 76 | Monaco ESM sandbox switch | pages/editor-sandbox.html, esbuild.config.mjs, scripts/check-monaco-package-contract.mjs, tests/monaco-esm-plan.test.js, docs/cws-remote-code-compliance.md |
The sandbox can leave deprecated AMD only if it imports packaged ESM assets and keeps fallback behavior [S17, S24] | Switched the sandbox to local ESM CSS/import loading, removed AMD copy steps, rejected AMD loader regressions, and added sandbox script parsing coverage |
| 77 | Monaco ESM fallback harness | tests/monaco-esm-sandbox-loader.test.js, pages/editor-sandbox.html |
Browser-profile proof can be blocked, but the loader/fallback contract still needs deterministic coverage [S17, S24] | Added a VM/DOM harness that executes the sandbox script, validates ESM path requests, ready posting, and missing-bundle fallback routing |
| 78 | Monaco ESM Chromium sandbox smoke | tests/e2e/monaco-esm-sandbox.spec.js, tests/e2e/helpers/extension-fixture.js |
The ESM sandbox switch must run in a real Chromium extension page, not only jsdom/VM harnesses [S17, S24] | Added a Playwright extension-page smoke for the packaged sandbox ready path and routed missing-bundle fallback path |
| 79 | Monaco adapter dashboard smoke | tests/e2e/monaco-adapter-dashboard.spec.js |
The ESM editor must persist real dashboard edits through the CodeMirror-compatible Monaco adapter [S17, S24] | Added a Playwright dashboard smoke for edit-open, adapter readiness, toolbar save, reload, and adapter value persistence |
| 80 | browser namespace alias |
src/shared/utils.ts, shared/utils.js, scripts/generate-ts-runtime-modules.mjs, pages/dashboard-firefox-compat.js, focused tests |
Chrome 148 exposes browser, so Chrome/Firefox code should converge without exposing extension APIs to userscript/page worlds [S25] |
Added a generated extension-context alias, fixed Chromium-vs-Firefox detection when browser.runtime exists, and pinned wrapper boundary coverage |
| 81 | Trusted Types author docs | README.md, pages/dashboard.html, tests/trusted-types-docs.test.js |
MAIN-world scripts on Trusted Types pages need explicit author guidance, while ScriptVault's default USER_SCRIPT path should stay documented as the safer default [S26] | Added README and Help guidance plus a static test that pins the docs and confirms no runtime policy shim was introduced |
| 82 | Subscription refresh scheduling | src/background/core.ts, settings defaults/schema/types, dashboard subscription controls, generated runtime artifacts, focused tests |
Chrome alarms remain the MV3-safe periodic work primitive, with same-name replacement and a 30-second minimum interval in current Chrome [S93] | Added a managed subscription refresh alarm, visible auto-refresh/interval controls, feed health labels, scheduler resync on add/remove/settings changes, and static contract coverage |
| 83 | Local workspace refresh status | pages/dashboard.js, src/storage/script-db.ts, modules/storage.js, focused dashboard/storage tests |
File System Access handles can persist in IndexedDB, but permission/read state must be visible because access can revert to prompt or fail between sessions [S81, S91, S92] | Added explicit bound/unchanged/applied/cancelled/error refresh state summaries for the editor local-file chip without exposing handles or absolute paths |
| 84 | Local workspace health evidence | src/background/core.ts, pages/dashboard.js, focused health/support tests |
Support snapshots need aggregate local-workspace evidence without file handles, paths, or local names [S81, S91, S92] | Added local workspace health counts, refresh-age buckets, and support-snapshot sanitization unless script inventory is opted in |
| 85 | Local refresh acceptance hardening | pages/dashboard.js, src/background/core.ts, focused local-workspace/local-health tests |
File System Access reads must reject oversized executable files before loading text, and parse/apply failures need distinct operator feedback [S81, S91, S92] | Added the 5 MB bound-file read cap, too-large and parse-failed status paths, and regression coverage for normal local apply registration |
| 86 | Greasy Fork publish preflight | pages/dashboard.html, pages/dashboard.js, tests/greasyfork-publish-handoff.test.js |
Greasy Fork documents read-only APIs plus multipart prefilled update forms, not a credentialed write API [S76] | Added editor publish preflight, metadata validation, new/update target detection, exact code preview, copy/download fallback, and static guards against background publish endpoints |
| 87 | Greasy Fork publication receipt | pages/dashboard.html, pages/dashboard.js, tests/greasyfork-publish-handoff.test.js |
Store-safe handoff needs a local receipt only after user-confirmed submission, without storing submitted code or account/session material [S76] | Added post-handoff confirmation, local-only publication receipt storage, Info-panel reload display, receipt trimming, and Chromium dashboard smoke coverage |
| 88 | Greasy Fork receipt history | pages/dashboard.js, tests/greasyfork-publish-handoff.test.js |
Greasy Fork still documents read-only APIs plus session-cookie prefilled form POSTs, so local fallback handling must not claim a credentialed publish API [S76] | Added per-script publication receipt history display, local-only clear-history management, source/account redaction copy, focused static coverage, and Chromium extension smoke coverage |
| 89 | Greasy Fork receipt summary fallback | pages/dashboard.js, tests/greasyfork-publish-handoff.test.js |
Clipboard writes are a user-initiated local action, while Greasy Fork publication still happens only through the user-reviewed prefilled form [S76, S94] | Added copyable sanitized receipt summaries for local publication history and Chromium smoke coverage that proves copied text omits source/account/session data |
| 90 | Greasy Fork receipt export fallback | pages/dashboard.js, tests/greasyfork-publish-handoff.test.js |
Local Blob URLs plus anchor download preserve a browser-native export path for sanitized local receipt text [S76, S95, S96] |
Added downloadable sanitized receipt summaries, safe receipt filenames, object URL revocation, focused static coverage, and Chromium smoke coverage for exported text redaction |
| 91 | Greasy Fork session-check polish | pages/dashboard.js, tests/greasyfork-publish-handoff.test.js |
Greasy Fork publication still depends on the user's browser session, so the preflight modal should let users open Greasy Fork without posting script data [S76] | Added a user-initiated Open Greasy Fork modal action that opens only the base URL with noopener/noreferrer, plus focused static coverage and Chromium smoke proof |
| 92 | Enterprise policy provisioning | manifest.json, managed-storage-schema.json, src/background/core.ts, pages/dashboard.js, docs/enterprise-policy-provisioning.md, focused manifest/runtime tests |
Chrome managed storage requires a manifest-declared schema; managed storage is read-only policy data and can be restricted to trusted contexts [S28, S97, S98] | Added schema wiring, trusted-context access narrowing, deterministic managed install tags, a dashboard Managed badge, and administrator docs |
| 93 | Enterprise policy diagnostics | src/background/core.ts, src/types/messages.ts, local health/support snapshot tests |
Chrome policy deployment is normally inspected at chrome://policy, but ScriptVault support snapshots need only aggregate extension-side evidence [S97, S98, S99] |
Added managed policy support/read/configuration/install counts and warning signals to local health without exposing policy values |
| 94 | GM value-sync support snapshot allowlist | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Chrome extension diagnostics should keep privileged userscript/storage state behind extension-controlled messaging and export only support-safe aggregates [S47, S98] | Added an explicit dashboard-side allowlist for GM value-sync local-health export data, including clamped retry-ready last-result evidence and known warning IDs only |
| 95 | GM value-sync support summary polish | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Support operators need pre-export visibility into aggregate local-health diagnostics while the privacy envelope keeps script/value data out of the UI and export path [S47, S98] | Cached local health during utilities refresh/export and added aggregate GM value-sync retry readiness to the support snapshot summary |
| 96 | GM value-sync retry-age diagnostics | src/background/core.ts, src/types/messages.ts, generated runtime artifacts, pages/dashboard.js, focused local-health/support tests |
Support diagnostics should distinguish fresh retry-ready write failures from stale ones while still exporting only aggregate local-health evidence [S47, S98] | Added sanitized retry-age minutes/buckets to last-result health and support-summary output |
| 97 | GM value-sync bounded retry history | src/background/core.ts, src/types/messages.ts, generated runtime artifacts, pages/dashboard.js, focused local-health/support tests |
Chrome storage quota guidance favors small JSON-serializable local state, and CWS user-data policy favors aggregate/anonymized operational diagnostics [S47, S98] | Added a five-entry aggregate retry-history store, local-health summary counts, support-snapshot allowlisting, and clear-all cleanup |
| 98 | GM value-sync stale retry cleanup | src/background/core.ts, src/types/messages.ts, generated runtime artifacts, pages/dashboard.js, focused local-health/support tests |
Chrome storage APIs support extension-local JSON state, and CWS user-data guidance favors minimal aggregate diagnostics for support exports [S89, S97] | Added seven-day retry-history retention, stale-entry pruning on sync persistence, local-health retained/stale counts, and support-snapshot allowlisting |
| 99 | GM value-sync retry resolution drill | tests/source-cloud-sync.test.js |
Empty-local-only retries should prove a transient write failure resolves on a later sync without widening stored or exported diagnostics [S89, S97] | Extended the write-failure fixture through a second sync that applies the preserved remote bundle and keeps retry result output identifier/value-free |
| 100 | GM value-sync retry-resolution health summaries | src/background/core.ts, src/types/messages.ts, generated runtime artifacts, pages/dashboard.js, focused local-health/support tests |
Support diagnostics need aggregate proof that retry-ready failures later cleared without exporting scripts, values, account data, or provider errors [S89, S97] | Added local retry-resolution records, support-safe health/export summaries, age buckets, and clear-all cleanup for resolution evidence |
| 101 | GM value-sync retry-resolution stale cleanup | src/background/core.ts, generated runtime artifacts, tests/local-health-report.test.js |
Local diagnostic records should keep the same retention boundary as support-safe history evidence [S89, S97] | Removed stale or malformed retry-resolution records during sync result persistence when no fresh resolution is written |
| 102 | GM value-sync resolution-history support evidence | src/background/core.ts, src/types/messages.ts, generated runtime artifacts, pages/dashboard.js, focused local-health/support tests |
Support diagnostics need bounded recent recovery evidence without exporting script/value/provider details [S89, S97] | Added a five-entry aggregate retry-resolution history, local-health/support summaries, stale-count reporting, and clear-all cleanup |
| 103 | GM value-sync retry-resolution export hardening | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Support exports should not overstate retry-resolution evidence from malformed local-health input [S47, S98] | Rejected malformed resolution records without prior retry-ready evidence, zeroed retained-history totals when entries sanitize to zero, and normalized history timestamp ranges |
| 104 | GM value-sync retry-resolution source invariants | tests/local-health-report.test.js |
Retry-resolution evidence must remain tied to successful clean retries after prior retry-ready history [S89, S97] | Added source-contract coverage for resolution record gates and persistence-time stale pruning of retry-resolution history |
| 105 | GM value-sync retry-resolution support summary polish | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Operators should see aggregate stale/excluded recovery evidence before exporting support snapshots [S47, S98] | Added support-card labels for historical retry-resolution applies and stale retry-resolution-history events excluded |
| 106 | GM value-sync support-summary clamp hardening | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Pre-export support summaries should format only non-negative integer aggregate counts [S47, S98] | Re-clamped all displayed GM value-sync support-summary counts before formatting |
| 107 | GM value-sync retry-resolution stale-history evidence | tests/local-health-report.test.js |
Stale retry-resolution history should stay visible only as aggregate exclusion evidence [S89, S97] | Added local-health source coverage for include-stale reads, stale exclusion counts, retained-entry filtering, typed output, and privacy flags |
| 108 | GM value-sync support-summary schema drift coverage | tests/support-snapshot-redaction.test.js |
Pre-export summaries should read only reviewed sanitized fields, not raw local-health input [S47, S98] | Pinned the exact sanitized GM value fields read by the support summary and rejected raw local-health field access |
| 109 | GM value-sync support export schema drift coverage | tests/support-snapshot-redaction.test.js |
Support exports should expose only reviewed aggregate diagnostic fields at every nested level [S47, S98] | Pinned the exact returned sanitizer keys for GM value sync, last-result, retry-resolution, retry-resolution-history, and retry-history exports |
| 110 | GM value-sync support privacy schema drift coverage | tests/support-snapshot-redaction.test.js |
Support export privacy metadata should stay explicit and false for sensitive data classes [S47, S98] | Pinned the exact nested privacy keys and false values for GM value sync support exports |
| 111 | GM value-sync support warning-count schema drift coverage | tests/support-snapshot-redaction.test.js |
Support exports should allow only reviewed GM value warning identifiers [S47, S98] | Pinned the exact warning-count allowlist and rejected raw warning-count key iteration |
| 112 | GM value-sync retry-age bucket schema drift coverage | tests/support-snapshot-redaction.test.js |
Retry-ready and retry-resolution support exports should share reviewed age buckets [S47, S98] | Pinned the exact retry-age bucket allowlist and unknown fallback for support exports |
| 113 | GM value-sync retry-resolution cleanup guard | tests/local-health-report.test.js |
Stale or malformed local retry-resolution records should be removed without writing null diagnostics [S89, S97] | Pinned the single-record cleanup helper and persistence-time remove path |
| 114 | GM value-sync retry-resolution history storage contract | tests/local-health-report.test.js |
Local retry-resolution history should retain only aggregate recovery evidence [S89, S97] | Pinned the exact stored retry-resolution history entry keys and rejected privacy/raw identifier fields |
| 115 | GM value-sync support summary phrase drift coverage | tests/support-snapshot-redaction.test.js |
Pre-export summaries should use only reviewed aggregate diagnostic wording [S47, S98] | Pinned fallback, opt-in, retry, history, stale, and capped-value summary phrases while rejecting raw identifier labels |
| 116 | GM value-sync support summary count-order coverage | tests/support-snapshot-redaction.test.js |
Pre-export summaries should present aggregate diagnostics in reviewed order [S47, S98] | Pinned baseline, retry, resolution, history, stale, warning, and final join order |
| 117 | GM value-sync support summary warning-total coverage | tests/support-snapshot-redaction.test.js |
Warning totals should be computed only from sanitized support-export warning counts [S47, S98] | Pinned sanitized warning-count reduction, shared count clamping, and capped/excluded aggregate wording |
| 118 | GM value-sync retry-resolution history type schema coverage | tests/local-health-report.test.js |
Typed local-health responses should expose only reviewed aggregate retry-resolution history fields [S89, S97] | Pinned retry-resolution-history response fields, privacy keys, and raw identifier exclusions |
| 119 | GM value-sync support summary fallback-state coverage | tests/support-snapshot-redaction.test.js |
Pre-export summaries should return reviewed fallback states before formatting counts [S47, S98] | Pinned sanitize-first unchecked/unavailable fallback order before aggregate count formatting |
| 120 | GM value-sync retry-resolution typed privacy coverage | tests/local-health-report.test.js |
Typed local-health responses should expose only reviewed aggregate retry-resolution fields and privacy keys [S89, S97] | Pinned single retry-resolution response fields, privacy keys, and raw identifier exclusions |
| 121 | GM value-sync retry-history typed privacy coverage | tests/local-health-report.test.js |
Typed local-health responses should expose only reviewed aggregate retry-history fields and privacy keys [S89, S97] | Pinned retry-history response fields, privacy keys, and raw identifier exclusions |
| 122 | GM value-sync typed privacy coverage | tests/local-health-report.test.js |
Typed local-health responses should keep the top-level GM value sync diagnostic envelope reviewed [S89, S97] | Pinned top-level GM value sync response fields, privacy keys, and raw identifier exclusions |
| 123 | GM value-sync last-result typed schema coverage | tests/local-health-report.test.js |
Typed local-health responses should keep persisted sync result diagnostics aggregate-only [S89, S97] | Pinned last-result response fields, retry-age fields, and raw identifier/privacy exclusions |
| 124 | GM value-sync support unavailable-state wording coverage | tests/support-snapshot-redaction.test.js |
Unavailable pre-export summaries should stay generic and support-safe [S47, S98] | Pinned generic unavailable wording and rejected provider/account/credential/script/key/error detail |
| 125 | GM value-sync last-result support export clamp coverage | tests/support-snapshot-redaction.test.js |
Support exports should not overstate retry-ready last-result evidence [S47, S98] | Pinned retry-ready clamping to sanitized failure/preserved counts and retry-age gating |
| 126 | GM value-sync support unchecked-state wording coverage | tests/support-snapshot-redaction.test.js |
Unchecked pre-export summaries should stay generic and support-safe [S47, S98] | Pinned generic unchecked wording and rejected provider/account/credential/script/key/error detail |
| 127 | GM value-sync last-result timestamp sanitizer coverage | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Support exports should normalize last-result timestamps through the reviewed helper [S47, S98] | Routed last-result timestamp export through sanitizeSupportSnapshotTimestamp() and pinned the shared-helper path |
| 128 | GM value-sync retry-age unknown bucket coverage | src/background/core.ts, background.core.js, tests/local-health-report.test.js |
Retry-ready diagnostics with missing timestamps should not be labeled fresh [S47, S98] | Classified null/undefined retry ages as unknown and pinned the local-health last-result gating path |
| 129 | GM value-sync support nested-field coverage | tests/support-snapshot-redaction.test.js |
Pre-export support summaries should read only reviewed nested sanitized fields [S47, S98] | Pinned nested last-result, retry-resolution, retry-resolution-history, and retry-history field allowlists |
| 130 | GM value-sync retry-history timestamp retention coverage | tests/support-snapshot-redaction.test.js |
Support exports should not retain retry-history timestamps when retained history is empty [S47, S98] | Pinned retained-history timestamp helper use for retry and retry-resolution histories |
| 131 | GM value-sync retry-resolution timestamp range coverage | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Support exports should not expose impossible retry-resolution timestamp ranges [S47, S98] | Clamped retry-resolution latest retry timestamp to the resolution timestamp before export |
| 132 | GM value-sync retry-resolution age-bucket gating | pages/dashboard.js, tests/support-snapshot-redaction.test.js |
Support exports should not retain retry-resolution age buckets without age minutes [S47, S98] | Gated retry-resolution age bucket export on retained age minutes and defaulted missing evidence to unknown |
| Capability | ScriptVault | Tampermonkey | Violentmonkey | ScriptCat |
|---|---|---|---|---|
| MV3 native | Yes | Yes | No (dead on Chrome) | Yes |
| Open source | MIT | No | MIT | GPL-3.0 |
| Chrome Web Store | Published | Published (12M) | Blocked (MV2) | Published |
| GM API (35+) | Yes | Yes | Yes | Yes |
| Monaco editor | Yes | No | Yes (MV2) | No |
| DevTools panel | Yes | No | No | No |
| Side panel | Yes | No | No | No |
| Script signing (Ed25519) | Yes | No | No | No |
| AST analysis (31 detectors) | Yes | No | No | No |
| Cloud sync providers | 7 | 6 | 4 | Built-in |
| Update diff + review inbox | Yes | No | No (most-requested) | No |
| Version rollback | Yes (3) | No | No | No |
| Import quarantine | Yes | No | No | No |
| Sigstore provenance | Yes | No | No | No |
| Workspaces | Yes | No | No | No |
| Command palette | Yes | No | No | No |
| Performance budgets | Yes | No | No | No |
| Background/cron scripts | Partial | No | No | Yes |
| Enterprise provisioning | Yes (Chrome/Edge) | Yes (v5.5) | No | No |
| MCP/AI integration | No | Yes (v5.5) | No | No |
| Firefox published | No (AMO-ready) | Yes | Yes | Yes |
| Edge published | No (pkg-ready) | Yes | No | Yes |
Items below were identified by exhaustive repo walk + 35+ external sources. Duplicates against existing Now/Next/Later/UC/Rejected tiers were filtered. Each item carries impact (1-5), effort (S/M/L/XL), and tier recommendation.
Items below identified by exhaustive repo walk + 40+ external sources across competitors (Tampermonkey v5.5.0, Violentmonkey MV3 status, ScriptCat v1.4.0-beta.4), Chrome 140-148 APIs, Firefox 149-153, security landscape (NSA MCP guidance, EU CRA Sep 2026, Trusted Types Baseline), and dependency changelogs. Deduplicated against all existing tiers (Now through Rejected) and all prior RD-1..RD-14 additions.
Verified-but-unfixed items from the 2026-07-02 deep audit. The audit shipped fixes for GM handler auth binding, attribute-injection XSS, the Chrome-as-Firefox misdetection, editor keystroke/cursor/undo bugs, trash-restore + backup-import data loss, and the cloud-sync tombstone-resurrection data loss (see CHANGELOG v3.16.0). The items below were confirmed reachable but deferred as higher-risk or larger than an audit fix.
Added 2026-07-01. Items below are net-new from the 2026-07-01 research pass and do not duplicate the existing Now/Next/Later/N-/X-/L-/UC- items. Sources in the Research-Driven Sources (2026-07-01) appendix.
Net-new from the 2026-07-02 pass (v3.16.0). Verified as not already implemented in code and not duplicating the Next tier, the Deep Audit Findings (2026-07-02), or the 2026-07-01 Research-Driven Additions. Cross-references: the Next-tier "editor cursor position stuck at Ln 1, Col 1" item is RESOLVED in v3.16.0 (monaco-adapter now caches the real cursor) — treat as done. One-click GreasyFork/OpenUserJS publish (VM #2425) is already covered by X-9 (publish handoff) — not re-added. UC-3 (AI-Assisted Script Editing) precondition "on-device LLMs practical" is now MET (Chrome Prompt API stable for extensions since Chrome 138) — see the P2 AI item below to promote it.
| ID | Source | URL |
|---|---|---|
| RD28-01 | TM per-script isolated cookie jars | Tampermonkey/tampermonkey#2815 |
| RD28-02 | TM fake crypto-exploit userscripts | Tampermonkey/tampermonkey#2783 |
| RD28-03 | TM streaming GM.fetch request | Tampermonkey/tampermonkey#1278 |
| RD28-04 | TM MV3 GM_xhr DNR serialization | Tampermonkey/tampermonkey#2215 |
| RD28-05 | ScriptCat AI Agent | scriptscat/scriptcat#1324 |
| RD28-06 | ScriptCat request-scoped DNR | scriptscat/scriptcat#1377 |
| RD28-07 | ScriptCat v1.4.0 release notes | https://github.com/scriptscat/scriptcat/releases/tag/v1.4.0 |
| RD28-08 | GreasyFork SRI enforcement request | greasyfork-org/greasyfork#1070 |
| RD28-09 | Chrome Prompt API (Gemini Nano) | https://developer.chrome.com/docs/ai/prompt-api |
| RD28-10 | Chrome built-in AI overview | https://developer.chrome.com/docs/ai/built-in |
| RD28-11 | VM restrict-to-current-site cluster | violentmonkey/violentmonkey#2410 |
| RD28-12 | GreasyFork account-takeover propagation | greasyfork-org/greasyfork#682 |
| RD28-13 | VM local-directory sync | violentmonkey/violentmonkey#2125 |
| RD28-14 | VM git-server sync | violentmonkey/violentmonkey#2176 |
| RD28-15 | File System Observer API | https://developer.chrome.com/blog/file-system-observer |
| RD28-16 | VM hold-execution-until-sync | violentmonkey/violentmonkey#2067 |
| RD28-17 | TM partitioned-cookie/CHIPS download | Tampermonkey/tampermonkey#2419 |
| RD28-18 | TM SR-inaccessible delete controls | Tampermonkey/tampermonkey#2813 |
| RD28-19 | TM Firefox container force-enable | Tampermonkey/tampermonkey#2792 |
| RD28-20 | Same-document View Transitions Baseline | https://web.dev/blog/same-document-view-transitions-are-now-baseline-newly-available |
Net-new from the 2026-07-09 pass. Deduped against ROADMAP.md, Roadmap_Blocked.md, RESEARCH.md, README v3.18.0, and existing RD28 sources.
Net-new from the 2026-07-16 pass (baseline v3.20.0). The prior RESEARCH.md's 10
opportunities all shipped (telemetry auth, vendor-import quarantine, URL
minimization, typed dispatch, source maps, WCAG 2.2 gate, locale/plural catalogs,
fail-closed smokes, unified release preflight, TS7). A competitive sweep confirmed
the 2026-H2 GM-API deltas competitors added — GM_audio, request-scoped cookie
partitioning + anonymous downloads, @unwrap, Navigation-API onurlchange,
CAT_userConfig, on-disk auto-reload (FileSystemObserver) — are ALREADY shipped
(verified in wrapper-builder.ts/parser/core.ts/dashboard.js), so they are
not re-added. SBOM (check-cra-sbom.mjs) already exists — not re-added. Items
below are verified against source and deduped against ROADMAP.md, Roadmap_Blocked.md,
CLAUDE.md audit history, and RESEARCH.md rejected ideas.
-
P1 — Wire or honestly gate the persistent UserCSS engine Why:
UserStylesEngine.registerStyle/toggleStyle/updateCSS/importUserCSS/importStylusBackup/onTabUpdated/onTabRemoved/isUserCSSUrlare exported and documented as shipped, but have no message-router action and notabs/webNavigationlistener wiring; onlyuserStylePreviewDraft/userStyleClearPrevieware reachable..user.cssinstall/persist is non-functional beyond ephemeral editor preview. Evidence: code audit —src/modules/userstyles.ts(exports ~1548-1570), unwired in generatedbackground.js; reachable actions atbackground.js:11843-11883,pages/dashboard.js:13364/13392; README listsmodules/userstyles.js.user.csssupport as a feature. Touches:src/background/core.ts(router +chrome.tabs.onUpdated/onRemovedorwebNavigation.onCommittedwiring),src/modules/userstyles.ts,pages/dashboard.js(install/toggle UI), README. Acceptance: either a user can install and persist a.user.cssstyle that injects on navigation to matching tabs (with a regression test provingonTabUpdatedinjection), OR the persistent half is explicitly feature-flagged off and the README/CLAUDE claim corrected to "editor preview only." Complexity: L -
P1 — Bump esbuild devDependency floor to
^0.28.1Why:esbuild ^0.28.0is below the0.28.1fix for GHSA-G7R4-M6W7-QQQR (Windows dev-server path traversal / arbitrary file read, CVSS 7.5); the build runs on Windows. Evidence: security research — https://github.com/advisories/GHSA-g7r4-m6w7-qqqr ;package.json:107. Touches:package.json,package-lock.json. Acceptance:esbuildresolves to ≥ 0.28.1;npm run build:prodand full suite green;npm auditstill 0. Complexity: S -
P1 — Add SECURITY.md and enable GitHub private vulnerability reporting Why: No
SECURITY.mdand no confidential intake exist; CRA vulnerability/incident reporting begins 2026-09-11 and downstream redistributors expect a coordinated-disclosure channel. Cheap, high trust signal; individual MIT maintainer is outside manufacturer duties but the channel is now baseline. Evidence: security research + RESEARCH.md open question; https://digital-strategy.ec.europa.eu/en/policies/cra-open-source ; absentSECURITY.md. Touches:SECURITY.md(new), repo settings (private vuln reporting), README security section. Acceptance:SECURITY.mddocuments supported versions, disclosure window, and contact; GitHub private vulnerability reporting enabled; a static test pins the file's presence and required sections. Complexity: S -
P1 — Re-run AST risk analysis on update bodies and diff the risk delta Why:
applyUpdategates@requireTOFU-SRI + provenance and flags cross-registry source changes (sourceIdentityChanged), but never callsScriptAnalyzer.analyzeAsynconnewCode. A malicious update from the SAME author/registry (GreasyFork account-takeover propagation — the dominant real-world userscript kill chain) applies with no risk-delta review. Evidence: code read —src/background/core.ts:1980-2094(no analyzer call;analyzeScriptexists atcore.ts:7346); security research — https://www.waze.com/discuss/t/urgent-two-scripts-were-compromised-on-feb-1-please-read-if-you-use-scripts/365499 Touches:src/background/core.ts(applyUpdate/checkForUpdates),bg/analyzer.ts, update-review UI inpages/dashboard.js,tests/core-flows.test.js. Acceptance: an update that introduces new network/credential/eval sinks vs. the prior version surfaces a risk-delta flag in the update-review inbox before auto-apply (or blocks auto-apply per setting); regression test covers a benign update (no flag) and a sink-adding update (flag). Complexity: M
-
P2 — Fix the UserCSS preview lifecycle (three leaks) Why: Closing/navigating the dashboard leaves injected preview CSS on the target page (only a
beforeunloadunsaved-guard exists, nopagehide/visibilitychangeteardown — the DevTools panel does it right);onTabUpdatedre-runsinsertCSSeven when CSS is unchanged (duplicate stacking); switching the active target tab during preview orphans the prior tab's sheet. Evidence: code audit —pages/dashboard.js:18152-18155(only teardown), cf.devtools-panel.js:376;src/modules/userstyles.ts:1453-1474(unconditionalinsertCSS);pages/dashboard.js:13373-13417+src/modules/userstyles.ts:843-872(active-tab-switch orphan). Touches:pages/dashboard.js(singleuserCssPreviewteardown owner +pagehide/visibilitychange),src/modules/userstyles.ts(onTabUpdatedno-op guard whenpreviousCss === css; clear prior tab before injecting into a newly-resolved tab). Acceptance: closing the dashboard mid-preview clears preview CSS from the target tab; repeatedonUpdatedevents do not stack duplicate sheets; switching target tabs clears the previous tab's preview; regression tests cover all three. Complexity: M -
P2 — Add a manifest permission-drift gate to the test suite Why: Nothing fails the build if
permissions/host_permissionsgrow beyond the intended set — the exact vector abused by 2026 CWS ownership-transfer/permission-creep attacks (QuickLens, ShotBird).store-copy:checkverifies disclosure coverage, not growth. Evidence: security research — https://pluto.security/blog/chrome-extension-supply-chain-attacks-permission-creep/ ;manifest.jsonpermissions set. Touches:scripts/(new drift check or extend an existing manifest check),tests/,package.jsoncheckwiring, README permission statement. Acceptance: a pinned permission/host allowlist; the build fails ifmanifest.json/manifest-firefox.jsondeclare any permission or host outside it; README documents the pinned set and the "never<all_urls>beyond current" commitment. Complexity: S -
P2 — Harden the build chain against npm lifecycle-script worms Why: Zero RUNTIME deps does not defend against install-time
preinstall/postinstallpayloads (Shai-Hulud / Mini-Shai-Hulud, 2026 H2). A repo.npmrcignore-scripts=truewith an explicit allowlist for deps that genuinely need a build step (esbuild, puppeteer-core) closes the lifecycle path. Evidence: security research — https://www.microsoft.com/en-us/security/blog/2025/12/09/shai-hulud-2-0-guidance-for-detecting-investigating-and-defending-against-the-supply-chain-attack/ Touches:.npmrc(new/edit), release docs, CLAUDE.md build notes. Acceptance:npm cisucceeds with lifecycle scripts disabled by default and only the allowlisted build steps run; documented publish-token discipline (publish-only scope, 2FA/OIDC); a note pins the policy. Complexity: S
-
P3 — Sanitize page-controlled template tokens Why:
resolveTemplateTokenssubstitutesactiveTab.title(fully page-controlled) into new-script source viasplit/joinwith no CR/LF stripping; a crafted multi-linedocument.titlecan append lines past the@namemetadata directive. Low impact (user reviews before save) but untrusted page data reaches executable source unsanitized. Evidence: code audit —pages/dashboard.js:13644-13676. Touches:pages/dashboard.js(resolveTemplateTokens), a focused test. Acceptance: token values have control characters (\r/\n) stripped and length clamped before substitution; regression test with a multi-line malicious title asserts the generated@nameline is single-line. Complexity: S -
P3 — Compress backup blobs with the Compression Streams API Why:
BackupSchedulerstores full uncompressed ZIP blobs inchrome.storage.local(known inefficiency, CLAUDE.md). The Baseline Compression Streams API (gzip/brotli) shrinks the footprint with no new dependency. Evidence: CLAUDE.md "Known Remaining Issues"; https://developer.mozilla.org/en-US/docs/Web/API/CompressionStream/CompressionStream Touches:src/modules/backup-scheduler.ts, restore path, migration for existing uncompressed blobs, focused tests. Acceptance: new backups are stored compressed with transparent decompress-on-restore; existing uncompressed backups still restore; measured storage reduction recorded in a test. Complexity: M -
P3 — Verify PRIVACY.md and CWS listing disclosures before Limited-Use enforcement (2026-08-01) Why: CWS Limited Use / Disclosure enforcement starts 2026-08-01; disclosures must match the zero-telemetry reality and enumerate all local data classes (Storage Buckets, opt-in sync/backup egress). Prior research flagged PRIVACY.md drift (Storage Buckets omitted, sync/backup egress under-described). Evidence: platform research — https://developer.chrome.com/blog/cws-policy-updates-2026 ;
PRIVACY.md(12.5K, present). Touches:PRIVACY.md, CWS listing copy,store-copy:checkcoverage. Acceptance: PRIVACY.md and the CWS/AMO listing enumerate every local storage surface and every opt-in network egress path;store-copy:checkasserts the disclosure covers each declared permission; no undisclosed data flow remains. Complexity: S
- ScriptCat niche directives —
CAT_fileStorage(per-script file storage),@storageName(shared cross-script namespace),@definition(.d.tseditor hints),@early-start. Verified absent; low demand and marginal over Chrome's existingdocument_start+ shippedlib/scriptvault.d.ts. Reconsider on user signal. Source: docs.scriptcat.org/docs/dev/meta. - On-device "explain this script" via Chrome Prompt API (Chrome 148 stable) — could summarize what an installed/updating script does using the on-device model, strictly opt-in and local. Philosophy tension with any data flow; gate behind explicit per-use consent. Source: https://developer.chrome.com/docs/ai/prompt-api