poli0981andClaude Opus 5.5 d9e5815dfe ci: SonarCloud CI analysis with coverage, and a release that never installs while holding a write token
SonarCloud ran Automatic Analysis: no coverage, and a scan of the repo rather
than of what CI builds. sonarcloud.yml replaces it — full-history checkout,
the coverage run, then the scan with the package version as the new-code
baseline. It is its own workflow so a Sonar outage or gate opinion can never
turn CI red, the scan action is pinned to a commit because it holds
SONAR_TOKEN, the token reaches only the two steps that use it, and runs
without secrets (Dependabot, forks) skip with a notice instead of failing.

Coverage now measures every src/**/*.ts module and emits lcov, but the CI
gate is unchanged: a glob threshold applies the docs/11 §1 numbers to
src/lib/core/** only (verified to still fail a run below them).

Hardening, from SonarCloud's findings and the scripts/config audit:
- npm ci --ignore-scripts everywhere, with `wxt prepare` run explicitly;
- checkouts drop persisted credentials;
- release.yml is split: gates and zip run with a read-only token; only a
  job that installs nothing and runs no repo code creates the Release; the
  store submit uses the local wxt binary, never `npx` with secrets in scope;
- reusables get named secrets instead of `inherit`. The announce job could
  never have worked: this repo stores RELEASES_WEBHOOK/REPO_WEBHOOK, the
  reusable reads DISCORD_*, and inherit passed neither;
- CI runs `npm audit --omit=dev`, which docs/09 already claimed it did;
- a non-required Windows smoke job (guard + unit tests).

serializeMarkdown's trailing-newline trim used /\n+$/, which backtracks
quadratically over a long newline run that is not at the end (S8786); it is
now a single backward scan, with a 20k-newline regression test.

docs/12 no longer copies the workflow YAML — the copies drifted three times,
and under docs-win a stale copy invites reverting a pinned action.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 00:06:52 +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

Requires Chrome 136 or later (April 2025), or any Chromium browser of the same vintage — Edge, Brave, Vivaldi, Opera. On an older browser the store keeps the version you already have and simply stops updating it.

From source (Node.js 26):

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%