Six Dependabot alerts (1 critical, 3 high, 1 medium, 1 low) plus six further `npm audit` highs, all in transitive DEV dependencies whose parents pin them to vulnerable ranges. That pinning is why Dependabot's own per-package PRs could not fix any of them — every one of those runs failed. `overrides` is the npm mechanism for precisely this case. shell-quote 1.7.3 -> ^1.9.0 wxt > web-ext-run > fx-runner adm-zip 0.5.18 -> ^0.6.0 wxt > web-ext-run > firefox-profile tmp 0.2.5 -> ^0.2.6 wxt > web-ext-run uuid 8.3.2 -> ^11.1.1 wxt > web-ext-run > node-notifier esbuild 0.27.7 -> ^0.28.1 vite, wxt, unplugin brace-expansion 1.1.16 -> ^5.0.8 web-ext-run > multimatch > minimatch The last one is the whole second cluster: `npm audit` reported six highs that were one brace-expansion DoS propagating through minimatch -> multimatch -> web-ext-run -> wxt, with fixAvailable:false because multimatch pins minimatch. `npm audit` now reports 0. It already reported 0 for `--omit=dev`, and still does: the shipped extension has no runtime dependencies, so none of this was ever in the artifact. Correcting something I wrote in the dependabot.yml comment and repeated in a PR: I said these advisories had "no reachable patched version". That was wrong — every one of them had a patched version. What they lacked was a path Dependabot could take on its own. Re-verified after the overrides: lint, check, knip, coverage, guard, build, check:manifest and zip all pass, and the built manifest is still exactly ["bookmarks","storage"] at version 1.0.0. ⚠️ Four of the six live only under web-ext-run, the Firefox dev runner behind `npm run dev:firefox` — a v1.0 non-goal per docs/00 §7, and the one script no gate exercises. docs/09 §3.1 records that, plus when each override can be dropped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
BookmarkMagic
Move your bookmarks between browsers the simple way: with a file. No account, no cloud sync, 100% offline.
A Chrome (MV3) extension for importing, exporting and editing bookmarks and folder trees. English · Tiếng Việt · 日本語.
Screenshots
| Edit | Export |
|---|---|
![]() |
![]() |
| Settings | About |
|---|---|
![]() |
![]() |
What it does
- Import HTML, JSON or CSV bookmark files, with a full preview first — counts, folders, depth, duplicates and warnings before anything is written.
- Choose how: into a new dated folder (the safe default), merged into your existing folders, or replacing everything. Replace saves a JSON safety backup first and deletes nothing until that backup is proven.
- Export everything, or just the folders you pick, to HTML (Chrome, Edge, Brave, Firefox, Safari, Vivaldi, Opera), JSON, CSV or Markdown.
- Edit the tree: search, rename, drag & drop, create folders, delete, and find duplicate links — every action reachable from the keyboard.
Privacy
This is the whole point of the project, so it is worth being precise.
- No network access at all. Not analytics, not telemetry, not update pings.
There is no server. A grep gate (
npm run guard) fails the build if anyone addsfetch,XMLHttpRequest,WebSocket,EventSourceorsendBeacon. - Exactly two permissions:
bookmarksandstorage. No host permissions, no content scripts, no background worker. Two gates enforce it: a unit test overwxt.config.ts, andnpm run check:manifest, which CI runs against the builtmanifest.json— because a build can add what the config never asked for. - Zero runtime dependencies. Nothing third-party ships in the extension.
- Settings use
chrome.storage.local, neverstorage.sync, so even your preferences stay off any vendor cloud.
Full policy: legal/PRIVACY.md.
Honest limitations
- Favicons cannot be imported — the bookmarks API has no favicon field.
- Imported bookmarks get today's date. Chrome does not let an extension set a bookmark's original creation date. Your exported files keep the real ones.
- CSV is a flattened view: empty folders and "which folder is the toolbar" are not preserved. Use HTML or JSON for a faithful backup.
- Markdown is share-only — BookmarkMagic cannot read it back.
Install
From the Chrome Web Store: ⚠️ link once the listing is live.
From source:
npm ci && npm run build
Then load .output/chrome-mv3/ at chrome://extensions with Developer mode on.
Development
npm run dev
npm run verify is the gate everything else answers to — lint, type-check,
knip, the grep gate and the test suite, in that order. It must be green before
every commit.
The docs/ directory is the binding specification, not notes: where
code and docs disagree, the docs win. Start with CLAUDE.md, then
docs/00–docs/02.
Contributing
Bug reports and translation fixes are welcome via issues. A bug report about parsing is far more useful with a sanitized sample of the file that broke.
Security issues: please follow SECURITY.md rather than opening
a public issue.
Support development
Entirely optional — BookmarkMagic is free software either way.
GitHub Sponsors · Ko-fi · Buy Me a Coffee · Patreon · PayPal
Licence
GPL-3.0-or-later. Also see legal/EULA.md,
legal/DISCLAIMER.md and
legal/THIRD_PARTY_NOTICES.md.
Not affiliated with or endorsed by Google, Chrome, or any browser vendor. Browser names are trademarks of their respective owners.



