build(deps): bump nanoid to 3.3.18 to clear GHSA-2v37-7h3g-55p8
`main` is red on `npm audit`. The advisory is `nanoid <3.3.17`, reached through `vite → postcss → nanoid`, and it was published after the last Dependabot run — so #19's green `npm audit` was a stale check, and bumping vite 8.1.5 → 8.2.0 did not move it: 8.2.0 still resolves `postcss@8.5.23` and `nanoid@3.3.16`. Lockfile only, three lines, transitive: 3.3.16 → 3.3.18. `package.json` is untouched, so this is not a dependency decision — it is the same bump `npm audit fix` performs, taken now because the branch it was blocking is already on `main` and SECURITY §7 does not relax `npm audit`. Verified after a clean `npm ci`: 0 vulnerabilities, 96 tests, typecheck and build all pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
4710841caa
commit
4f15936f5a
1 file changed
+3
-3
Generated
+3
-3
@@ -3570,9 +3570,9 @@
|
||||
"license": "MIT"
|
||||
},
|
||||
"node_modules/nanoid": {
|
||||
"version": "3.3.16",
|
||||
"resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.16.tgz",
|
||||
"integrity": "sha512-bzlKTyNJ7+LdGIIwy8ijFpIqEQIvafahV7eYykJ8Cvh42EdJeODoJ6gUJXpQJvej1BddH8OqTXZNE/KfbWAu8Q==",
|
||||
"version": "3.3.18",
|
||||
"resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.18.tgz",
|
||||
"integrity": "sha512-DTg4MJbGMWkfi6VZFdNt2/caMbQy4Ou+Op/hJQvGEWcnVfoA1QA+xzRKAzw9jD6+GVOOeYr/mIcuDSdug6F6+w==",
|
||||
"dev": true,
|
||||
"funding": [
|
||||
{
|
||||
|
||||
Reference in new issue
Block a user