poli0981andClaude Opus 5 b1698aca0b ci: stop CI being red for a reason nobody acts on, and gate the manifest key set
notify-ci-failure.yml called a reusable that declares DISCORD_CI_WEBHOOK as
`required: true`, which GitHub validates before any of the reusable's own logic
runs. With the secret unset — docs/00 §10.6 lists it as still open — that
workflow failed on *every* CI completion, success included, from the first push
after it landed. The file's own header comment admitted it. This is precisely
the failure mode commit 5f4c6e7 fixed for releases: a run that is red for a
reason nobody acts on teaches everyone to stop reading the colour, and the next
genuine failure goes unnoticed.

release.yml's `gh release create` had no existence check, so any failure after
it — realistically the CWS publish step, once autopublish is on — stranded the
tag: a re-run could not get past that line, and recovery meant deleting the
Release and the tag by hand. v1.0.1 is the first tag to exercise that path at
all, since both the continue-on-error announce fix and tag_override landed
after the v1.0.0 tag object.

check-manifest.mjs now asserts the exact top-level key SET, not just the absence
of ten enumerated reach-widening keys. The forbidden list can only catch what
someone thought to name; this catches a build tool that starts emitting a key
nobody asked for. That matters immediately: WXT is a 0.x dependency, so a
routine minor bump is exactly when it happens, and tests/unit/manifest.test.ts
is structurally blind to it — it reads wxt.config.ts, which a WXT upgrade cannot
change. Verified by injecting a `commands` key into a built manifest and
watching the gate fail.

docs/12's sample YAML updated in the same commit, so the drift this phase just
finished correcting does not immediately start again.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-03 19:16:12 +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 — the issue forms ask for what is needed, and none of them requires you to write code.

If a bookmark file will not import, that is the most useful report there is, because the sample becomes a permanent test. Sanitize it first:

node scripts/sanitize-bookmarks.mjs your-bookmarks.html

That strips every address and title but keeps the structure, encoding and timestamps a parser bug depends on — so the sanitized file still reproduces the problem without handing over your browsing history.

CONTRIBUTING.md has the rest: the setup, the rules that are not negotiable, and how a reported file becomes a regression test.

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%