Skip to content

v0.6.1 — clear every Dependabot alert

Latest

Choose a tag to compare

@hkoren hkoren released this 10 Sep 02:23
· 33 commits to main since this release
4e4f30d

Security housekeeping only — nothing user-facing changed. dist/ in this release is byte-identical to 0.6.0 for every package; only the version stamp and CHANGELOG.md differ. If you're consuming openTagCloud from npm, there is nothing here to gain by upgrading. This release exists so the repo builds and tests clean against a tree with no known advisories.

Every advisory below lived in the development tree. None of it was reachable from a published bundle, so no consumer was ever exposed.

The last open alert: vitest

GHSA-82fw-gwwq-j7x9 — path traversal / arbitrary file read via a @vitest/mocker redirect mock. @vitest/mocker registered a redirect target without checking it against the dev server's file-serving allowlist, so anything that could reach the Vite HMR socket could point a mock outside the project root and read the file back as module source.

Dependabot filed this seven times — once per workspace declaring vitest, plus two against the lockfile — but it was a single advisory with a single fix: 4.1.11, a major over the ^3.0.0 pinned in core, svelte, react, vue, and solid.

The major turned out to need no migration. All five vitest.config.ts files are jsdom plus a setup file, and nothing in that surface moved in v4. Verified before merging: 73 vitest tests, 10 Angular jest tests, 23 Playwright e2e tests, plus build, check, and lint — all green.

Two criticals that npm audit fix could not reach

next carried two unauthenticated-RCE advisories (GHSA-p293-qw3h-jr36, GHSA-2xp9-vwfh-vxw4) and neither npm audit fix nor npm update next would move it. The reason is worth recording: next reached the tree only as a peer dependency, and npm will not raise a peer on its own — so the lockfile sat on 16.3.0 no matter what was run against it.

The fix was to add next as a real devDependency at ^16.3.4. The peer range deliberately stays at >=13.0.0. Narrowing it would push every consumer onto a newer Next.js to resolve a vulnerability in this repo's own CI install, which is not their problem to absorb. The devDependency pins what we build and test against; the peer keeps stating what's actually supported.

Also cleared: fast-uri, browserslist, js-yaml, baseline-browser-mapping, and sharp.

npm audit now reports 0 vulnerabilities, and Dependabot has no open alerts.

Verifying the "no runtime change" claim

Rather than asserting it, the new build was packed and diffed against the published 0.6.0 tarball:

diff -rq old/package new/package | grep -v 'CHANGELOG.md|package.json'
(nothing)

Identical dist/ for both @opentagcloud/core and opentagcloud.

Full changelog: v0.6.0...v0.6.1