Repository navigation
deps: patch-level fixes for OSV-reported vulnerabilities - #882
Open
stamp-build[bot] wants to merge 1 commit into
Open
stamp-build[bot] wants to merge 1 commit into
stamp-build[bot] wants to merge 1 commit into
Conversation
zhiqiang asked to fix what has a fixed version (#superzz-botiverse:5e1e952b). The daily OSV scan (run 41631971568) reported 47 advisories in 16 packages. This change takes the ones fixable within the same major line via pnpm overrides; the lockfile is regenerated with pnpm 9.12.0. - undici 7.29.1 -> 7.30.1 (8 advisories) - electron 43.5.0 -> 43.8.1 (8) - nanoid@3 3.3.15 -> 3.3.18 (2) - postcss 8.5.15 -> 8.5.23 (2) - js-yaml@4 4.2.0 -> 4.3.2 (3) - browserslist 4.28.4 -> 4.28.7 (2) - baseline-browser-mapping 2.10.40 -> 2.11.0 (1) osv-scanner on the new pnpm-lock.yaml: 26 advisories gone; the 20 left in it are all major-version upgrades (vite 5->6 with its esbuild, vitest 2->3+, react-router 6->7, minimatch 3->11, sharp 0.34->0.35 via miniflare, @hono/node-server 1->2) and need code changes; container/package-lock.json has the same @hono/node-server advisory (1 more). Signed-off-by: NotZZ <botiverse+notzz@agents.stamp.build>
Contributor
Author
|
@bytemain CI 全绿了(worker 测试
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fix the OSV-reported vulnerabilities in
pnpm-lock.yamlthat have a fix in the same major line, viapnpm.overrides; lockfile regenerated with pnpm 9.12.0 (--lockfile-only).Why
zhiqiang (2026-11-03, #superzz-botiverse): fix what has a fixed version. Source: the daily OSV scan added in #881 (run 41631971568: 47 advisories in 16 packages).
Verification
osv-scanner scan source -L pnpm-lock.yaml(v2.7.0) on this head: 26 advisories gone, 20 remain in the pnpm lockfile, all needing a major upgrade (below).install --frozen-lockfile):packages/node32/32,packages/agent-session-store13/13,packages/cli198/198 (after building hands-node and agent-session-store, as CI does) pass;adminvite buildsucceeds.workertests could not run on this ARM host:better-sqlite3's native binding is not built there (environment, not this change).worker-tests.ymlruns on this PR because it touchespackage.jsonandpnpm-lock.yaml.Not in this PR (need code changes / owner decision)
@vitest/mocker.admin).@hono/node-server1 → 2 (1 inpnpm-lock.yaml, 1 incontainer/package-lock.json).