poli0981andClaude Opus 5 1c0da6f0e8 docs: write the runbooks a shipped extension needs
docs/13 had only a first-submission runbook, so nothing described how to ship
v1.0.1 — nor what to do when an update is rejected, when the item is taken
down, or when a tag was pushed and the release run died half-way. All four are
now reachable in a way they were not before the listing went public.

- docs/13: §1 marked historical (and its never-performed step 8 handed to
  docs/11 §5). New §1b update runbook — the bump must reach main *before* the
  tag, because release.yml compares the built manifest against the tag; the
  store artifact is the Release asset, not the CI artifact, because that is
  what SHA256SUMS.txt covers. New §7: a rejected update leaves the published
  version live, so it is not an emergency; a rejected version string can never
  be reused, so the fix ships as the next patch, not as a re-upload; and there
  is no rollback in CWS at all — only a higher version carrying the revert.
- docs/12: the sample YAML had drifted twice (setup-node v6 vs the live v7, and
  a missing check:manifest in the release job). Docs win here, so reconciling
  the wrong way would have downgraded a pinned action and deleted a gate — both
  fixed, with a note that this is the one doc where the running pipeline is the
  ground truth. §2.4 gains the if:/continue-on-error that stops
  notify-ci-failure failing on every green CI run for want of a secret.
  §5's checklist now distinguishes verified from unknown instead of reading as
  eight things nobody did.
- docs/11: §2's inventory named four fixtures that do not exist and omitted two
  that do; each phantom is removed only after naming the test that actually
  covers its behaviour. §5 gains the upgrade pass — installing the published
  build, updating over it, and proving the legal flag and settings survive —
  which is the only failure mode that hits every user at once. §6's parse
  budget gains a procedure now that a generator exists to make the file.
- docs/14 §3 stopped embedding drafts of documents users have already accepted
  (its copy still carried `Last updated: 2026-⚠️`). It now points at the
  committed files and specifies when a change bumps LEGAL_VERSION, since that
  re-shows the gate to everybody.
- SECURITY.md: supported versions (latest published only — Chrome auto-updates,
  so there is no population to back-port for), an email fallback for reporters
  without a GitHub account, and an honest split between "fix prepared in 14
  days" and "fix reaching users", which additionally needs store review.
- legal/PRIVACY.md: says what happens to a file you send us. Deliberately not a
  LEGAL_VERSION bump — it clarifies handling of data a user chooses to send,
  which was never inside "what the Extension collects", and re-gating every
  installed user over a clarification is the worse outcome.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-03 20:20:05 +07:00
2026-07-25 19:21:07 +07:00

BookmarkMagic

License: GPL-3.0-or-later CI CodeQL Runtime dependencies: 0

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
The edit tree, showing bookmarks with their domains The export tab: folder picker on the left, format cards on the right
Settings About
Settings: language, theme, and four defaults About: version, links, third-party statement, donate links and the legal block

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 adds fetch, XMLHttpRequest, WebSocket, EventSource or sendBeacon.
  • Exactly two permissions: bookmarks and storage. No host permissions, no content scripts, no background worker. Two gates enforce it: a unit test over wxt.config.ts, and npm run check:manifest, which CI runs against the built manifest.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, never storage.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: here

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.

S
Description
No description provided
Readme GPL-3.0
3 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 75.8%
Svelte 14.5%
JavaScript 9.2%
CSS 0.4%