Issue & discussion janitor log

[Mikola Lysenko (mikolalysenko)]

[agent] Janitor: the hourly issue and discussion janitor rewrites this log each run. It shows the last run, the actions it took with a reason for each, a rolling list of recent actions, deferred candidates, and anything that needs a human. The routine writes it to the janitor/ledger branch, and a workflow on that branch applies it here.

Last run

2026-10-25 13:20Z on origin/main 3db3cdf6 (#1705, merged 2026-10-24 02:54Z). No PR has merged since the last run (2026-10-24 13:21Z). Reviewed 130 open issues (all filed by the fleet account), the issues closed since 2026-10-24, and the PRs updated since 2026-10-23.

This run

• Issues closed: none. No PR merged, so nothing new is fixed on main. No new duplicates, obsolete, empty, spam or question issues. The one new issue, CI perf (coverage tradeoff): Windows-only path bugs reach main because test (windows-latest, *) runs only nightly #1720 (Windows tests only run nightly), carries agent:needs-human and overlaps Nightly Windows test shards fail on temp-path spelling (RUNNER~1 vs canonical \\?\ paths) #1689 only as context.
• Labels fixed: none needed. No closed issue still carries agent:claimed, and every bughunt issue has a pm:* label.
• Claims: all kept. Every open claimed issue has an open PR: Hosted npm pin in package-lock.json is attested by VEX in a Deno project, but deno.lock keeps installing the unpatched registry copy #406 (Warn when deno.lock keeps installing an npm package (#406) #1711), Global Go patching (-g) reports success and VEX attests not_affected, but tools already built with go install keep running the unpatched code, and nothing tells the user to reinstall them #422 (Fix global Go apply leaving installed tools stale (#422) #1717), Global mode can't see any Deno global install: the npm packages under $DENO_DIR/npm/registry.npmjs.org are never crawled, so scan -g misses them and Deno 2.9's per-tool node_modules gets patched and VEX-attested while the tool runs the unpatched copy #444 (Fix Deno global npm tools missed by -g (#444) #1719), Agent-mode rollback in the other scope (rollback -g after a project apply, or rollback after a -g apply) deletes the manifest entry and blobs while the patched copy stays patched, and exits 0 #450 (Fix rollback dropping records patched in the other scope (#450) #1714), On Composer 1, composer/installers packages (e.g. WordPress plugins) are invisible to the crawler: agent scan skips them as "not installed" and hosted vex attests them without checking the unpatched installed bytes #463 (Fix Composer 1 packages moved by composer/installers (#463) #1723), Agent-mode cargo patches the unused registry copy of a crate the user overrides with [patch.crates-io], and VEX attests not_affected while the build links the user's unpatched fork #506 (Fix cargo agent mode patching overridden crates (#506) #1715), Hosted uv scan wires a dynamic = ["dependencies"] project, but rollback, remove and the vendored takeover then always refuse ("pyproject.toml no longer declares six") #639 (Fix hosted uv pinning dynamic dependencies (#639) #1709), Hosted Hatch scan exits 0 "redirected" when [tool.uv.sources] pins the patched package, but Hatch's uv installer obeys the source: url/path sources install the unpatched wheel and git sources break every install #673 (Fix hosted Hatch ignoring uv sources (#673) #1706), Yarn classic VEX attests not_affected while a bundled copy of the patched package@version stays unpatched (yarn.lock has no inBundle, so the #325 fix can't see it) #758 (Fix yarn classic VEX ignoring bundled copies (#758) #1712), Agent-mode apply of a same-size PyPI patch in the same second as pip install leaves pip's __pycache__ bytecode valid, so Python keeps running the unpatched code while apply reports it patched #819 (Fix stale Python bytecode after apply (#819) #1722), Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 (Fix relocated Yarn pnpm store missed by agent (#859) #1721), Gem hosted and vendored lock pins ignore a gemspec development dependency on the same gem, so on Bundler 2.7+ the rewritten Gemfile.lock fails every frozen install ((= v)! vs Bundler's merged (>= 0, = v)!) #985 (Fix gem pins breaking frozen installs with gemspec dev deps (#985) #1718), uv hosted → vendored takeover onto a newer patch uuid fails "no installed package found on disk" (exit 1) when the venv holds the hosted patch's bytes, while --dry-run previews success #1105 (Fix hosted to vendored takeover onto a newer patch (#1105) #1713), Vendored re-runs outside the npm family exit 1 while a superseding patch is still building, instead of keeping the older vendored patch #1235 (Fix vendored re-runs failing on unserved upgrades (#1235) #1707), Nightly Windows test shards fail on temp-path spelling (RUNNER~1 vs canonical \\?\ paths) #1689 (CI: fix Windows nightly yarnrc path expectation (#1689) #1710). Vendored yarn classic wiring breaks every install run from a workspace member directory: yarn resolves the file:./.socket/vendor/… tarball against the member dir #691 and Hosted gem stale-install guard still flags an unused system gem-home copy under Bundler deployment or the .bundle default path, so scan --mode hosted --vex fails with no_applicable_patches on fresh checkouts #1109 carry agent:needs-human.
• Discussion ops: this log only. No issue closed since yesterday's drift comments, so the ledgers have no new drift.

Recent actions (rolling, newest first)

• 2026-10-25 13:20Z: no-op run (no merges since 3db3cdf6, no closes, no label fixes, no new ledger drift)
• 2026-10-24 13:21Z: removed agent:claimed from 30 closed issues (Vendored Poetry patches can't be reverted after a poetry lock from another Poetry major (1.8 ⇄ 2.x): vendor --revert drift-keeps every package with exit 0, and the "re-vendor" remedy is a no-op #1615, CI perf: floating toolchain versions in ci.yml e2e — upstream uv 0.13.2 red-mained the merge queue for 2.7 h (~4.3k job-min wasted on 10-20; ~0.45k min/day amortized) #1645, Hosted and vendored scans refuse an independent Bun project in a dot-directory (packages/.tools) as a workspace member, though Bun's packages/* never lists dot-directories, so that project can't be patched at all #1631, Hosted and vendored npm scans refuse to patch the project's own bundleDependencies (inBundle: true on root deps) as "bundled inside its parent's tarball", although npm installs those entries from the lock #1618, Vendored npm refusal of a lockfileVersion 4 lock says to remove patchedDependencies and re-run npm install, but npm 12 keeps the lock at v4, so the advice loops and vendoring stays refused #1576, repair leaves a pre-#1541 root <uuid>/.gitattributes as * -text, so the repaired Bun tarball goes back into Git LFS on the next commit #1581, Vendored scan exits 0 when .gitignore covers .socket/vendor/state.json, so the commit silently drops the ledger and every other checkout's rollback fails with vendor_ledger_missing #1638, Gem vendored remove / rollback / vendor --revert after a hosted→vendored takeover leave the patched .gem in vendor/cache with no warning, so fresh installs of the restored upstream lock keep installing patched bytes #1594, Yarn berry ignores an exec: copy of the patched package under another dependency name, so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1630, Hosted and vendored scans from a nested directory under a vlt.json root that is not a workspace member write its stray vlt-lock.json and exit 0, though vlt installs from the root there; VEX then attests not_affected (also vlt 1.3.8 pnpm-workspace.yaml dirs, contrary to #1574's premise) #1584, Hosted and vendored npm scans break npm 12 allowScripts pins ([email protected]), so approved install scripts are silently blocked (or every npm ci fails under strict-allow-scripts) #1595, VEX product purl from pyproject.toml keeps the raw version (pkg:pypi/[email protected]) instead of the PEP 440-normalized one that uv.lock, the wheel and SBOMs use (1.0.0rc1) #1589, Hosted gem rollback / remove after an unconverged superseding re-scan restore Gemfile.lock but leave the new patch's source … do block in the Gemfile, report success, and the next bundle install re-patches #1626, Vendored pnpm 10.34.2+ / 11 / 12 scan breaks build approvals (allowBuilds / onlyBuiltDependencies): the patched package's install script stops running, and on pnpm 11/12 every frozen install fails with ERR_PNPM_IGNORED_BUILDS #1597, Bun vendor --check says "wiring missing … re-run socket-patch vendor" when a git, folder or URL/file: tarball copy of the vendored package stays unpatched, though bun.lock still references the artifact and the remedy loops #1600, Hosted vlt scan tells users to try --mode vendored for a named-registry package, but vendored always refuses that package with vendor_lock_entry_unsupported #1601, Slow scan: poetry hosted 2.6x median ms/pkg (lock_fragments::rewrite_batch + VEX lock re-parse) #1473, Slow scan: pdm hosted 2.7x median ms/pkg (toml_edit parse of pdm.lock 14x: rewrite_batch + VEX extract) #1624, Vendored rollback and remove leave an unledgered .socket/vendor/npm/<uuid>/ artifact dir behind (e.g. the losing side of a merge), while vendor --revert sweeps it, and nothing afterwards reports it #1610, Hosted pnpm 12.0–12.12 rollback drops the scoped-registry tarball: URL pnpm recorded, so the restored lock isn't byte-exact #1619, Slow scan: vlt hosted 2.6x median ms/pkg (vlt::partition_instances / split_dep_id per patch) #1570, Vendored PyPI revert drift warnings print the ledger key in Rust debug form: Pipfile.lock entry for Some("default:six") changed since vendoring #1608, CI perf: coverage and e2e-build wait ~1.4 min for clippy on every run; clippy failed 0 of 256 PR runs in 7 days #1681, Nightly: gem unwind-after-unconverged-supersede e2e fails on bundler 1.17.3/2.1.4 #1685, Hosted gem: on Bundler < 2.2 locks a superseding patch is never applied (scan skips it as redirect_unattributable, exits 0) #1688, Hosted yarn classic offline-mirror refusal misses a mirror set in a workspace member's .yarnrc, so installs run from that member fail the integrity check while the scan reports success and VEX attests #1115, Yarn berry reads the wrong nodeLinker when a ${VAR} in .yarnrc.yml is set from .env.yarn: vendored falsely refuses a node-modules project, and agent misses a live PnP project #1611, Perf regression: bun-isolated/rescan wall +21% (cc938aa6..17793173; #1279 candidate) #1606, Vendored requirements.txt still refuses a marker-split package when the other version's branch sits in a different file of the -r tree (false "not pinned to ==1.16.0", exit 1), so a fresh install stays unpatched #1104, Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783)
• 2026-10-24 13:21Z: posted drift comments on ledgers Bug hunt ledger: npm #302 (Hosted and vendored npm scans break npm 12 allowScripts pins ([email protected]), so approved install scripts are silently blocked (or every npm ci fails under strict-allow-scripts) #1595, Vendored npm refusal of a lockfileVersion 4 lock says to remove patchedDependencies and re-run npm install, but npm 12 keeps the lock at v4, so the advice loops and vendoring stays refused #1576, Hosted and vendored npm scans refuse to patch the project's own bundleDependencies (inBundle: true on root deps) as "bundled inside its parent's tarball", although npm installs those entries from the lock #1618, repair leaves a pre-#1541 root <uuid>/.gitattributes as * -text, so the repaired Bun tarball goes back into Git LFS on the next commit #1581), Bug hunt ledger: pnpm #303 (Hosted pnpm 12.0–12.12 rollback drops the scoped-registry tarball: URL pnpm recorded, so the restored lock isn't byte-exact #1619, Vendored pnpm 10.34.2+ / 11 / 12 scan breaks build approvals (allowBuilds / onlyBuiltDependencies): the patched package's install script stops running, and on pnpm 11/12 every frozen install fails with ERR_PNPM_IGNORED_BUILDS #1597, Vendored scan exits 0 when .gitignore covers .socket/vendor/state.json, so the commit silently drops the ledger and every other checkout's rollback fails with vendor_ledger_missing #1638), Bug hunt ledger: Yarn classic (1.x) #304 (Hosted yarn classic offline-mirror refusal misses a mirror set in a workspace member's .yarnrc, so installs run from that member fail the integrity check while the scan reports success and VEX attests #1115, Vendored rollback and remove leave an unledgered .socket/vendor/npm/<uuid>/ artifact dir behind (e.g. the losing side of a merge), while vendor --revert sweeps it, and nothing afterwards reports it #1610, socket-patch --update on a yarn-classic-installed copy says "managed by npm": npm update -g leaves a yarn global add install stale, and a yarn project is told to run npm install #1629), Bug hunt ledger: Yarn Berry (2+) #305 (Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry reads the wrong nodeLinker when a ${VAR} in .yarnrc.yml is set from .env.yarn: vendored falsely refuses a node-modules project, and agent misses a live PnP project #1611, Yarn berry ignores an exec: copy of the patched package under another dependency name, so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1630), Bug hunt ledger: Bun #306 (On Bun 1.4, a bun patch made on a hosted or vendored package is silently dropped by the next superseding re-run, takeover, rollback or revert (the #367 guard only matches name@version keys) #1019, Bun vendor --check says "wiring missing … re-run socket-patch vendor" when a git, folder or URL/file: tarball copy of the vendored package stays unpatched, though bun.lock still references the artifact and the remedy loops #1600, repair leaves a pre-#1541 root <uuid>/.gitattributes as * -text, so the repaired Bun tarball goes back into Git LFS on the next commit #1581, Hosted and vendored scans refuse an independent Bun project in a dot-directory (packages/.tools) as a workspace member, though Bun's packages/* never lists dot-directories, so that project can't be patched at all #1631), Bug hunt ledger: vlt #307 (Hosted vlt scan tells users to try --mode vendored for a named-registry package, but vendored always refuses that package with vendor_lock_entry_unsupported #1601, Hosted and vendored scans from a nested directory under a vlt.json root that is not a workspace member write its stray vlt-lock.json and exit 0, though vlt installs from the root there; VEX then attests not_affected (also vlt 1.3.8 pnpm-workspace.yaml dirs, contrary to #1574's premise) #1584), Bug hunt ledger: pip / requirements.txt #309 (Vendored requirements.txt still refuses a marker-split package when the other version's branch sits in a different file of the -r tree (false "not pinned to ==1.16.0", exit 1), so a fresh install stays unpatched #1104), Bug hunt ledger: uv #310 (VEX product purl from pyproject.toml keeps the raw version (pkg:pypi/[email protected]) instead of the PEP 440-normalized one that uv.lock, the wheel and SBOMs use (1.0.0rc1) #1589, Hosted and vendored uv scans wire a patched wheel into a project that sets no-binary / no-binary-package for that package, so every later uv sync fails ("marked as --no-binary but is itself a binary distribution") #1603), Bug hunt ledger: Poetry #311 (Vendored Poetry patches can't be reverted after a poetry lock from another Poetry major (1.8 ⇄ 2.x): vendor --revert drift-keeps every package with exit 0, and the "re-vendor" remedy is a no-op #1615, VEX product purl from pyproject.toml keeps the raw version (pkg:pypi/[email protected]) instead of the PEP 440-normalized one that uv.lock, the wheel and SBOMs use (1.0.0rc1) #1589), Bug hunt ledger: Pipenv #313 (Vendored PyPI revert drift warnings print the ledger key in Rust debug form: Pipfile.lock entry for Some("default:six") changed since vendoring #1608), Bug hunt ledger: Bundler (RubyGems) #316 (Hosted gem rollback / remove after an unconverged superseding re-scan restore Gemfile.lock but leave the new patch's source … do block in the Gemfile, report success, and the next bundle install re-patches #1626, Gem vendored remove / rollback / vendor --revert after a hosted→vendored takeover leave the patched .gem in vendor/cache with no warning, so fresh installs of the restored upstream lock keep installing patched bytes #1594)
• 2026-10-22 13:20Z: removed agent:claimed from 8 closed issues (Hosted and vendored rewrites replace poetry.lock with a file owned by the user running socket-patch, so after a root scan (e.g. a Docker bind mount) the lock's owner gets "Permission denied" from poetry add / poetry lock #1635, Vendored vendor --revert / remove of a two-package pip lock pylock.toml writes an invalid lock: the first package's [packages.wheels.hashes] table moves under the next package, pip refuses the file, and the CLI exits 0 #1623, Hosted rollback / remove of a uv pip compile --no-build / --only-binary / --no-binary pylock.toml re-adds the artifacts uv filtered out (uv 0.9.16+), so the restore isn't the original lock #1613, Hosted uv rollback / remove ignore exclude-newer-package: on uv 0.12+ the restored uv.lock gains an sdist the per-package cutoff had excluded, so the restore isn't the original lock #1604, A requirements.txt pin spelled ===X, ==X.0 or ==vX doesn't contest another lock's Socket wiring of release X, so vex attests not_affected while pip install -r installs the upstream release (#1549 residual) #1602, A requirements.txt wheel path without a leading ./ (wheels/six-1.16.0-…whl) doesn't contest another lock's Socket wiring, so vex still attests not_affected while pip install -r installs the upstream wheel (#1549 residual) #1587, Vendored PyPI wheels aren't checked against .gitignore or Git LFS rules (*.whl, .socket/), so a vendored Pipenv scan exits 0 and every fresh clone's pipenv sync fails #1572, Vendored requirements.txt rewrite re-joins every line of a mixed CRLF/LF file with one terminator, so untouched lines change and vendor --revert / remove can't restore the file #1567)
• 2026-10-22 13:20Z: posted drift comments on ledgers Bug hunt ledger: pip / requirements.txt #309 (Vendored requirements.txt rewrite re-joins every line of a mixed CRLF/LF file with one terminator, so untouched lines change and vendor --revert / remove can't restore the file #1567, A requirements.txt wheel path without a leading ./ (wheels/six-1.16.0-…whl) doesn't contest another lock's Socket wiring, so vex still attests not_affected while pip install -r installs the upstream wheel (#1549 residual) #1587, A requirements.txt pin spelled ===X, ==X.0 or ==vX doesn't contest another lock's Socket wiring of release X, so vex attests not_affected while pip install -r installs the upstream release (#1549 residual) #1602, Vendored vendor --revert / remove of a two-package pip lock pylock.toml writes an invalid lock: the first package's [packages.wheels.hashes] table moves under the next package, pip refuses the file, and the CLI exits 0 #1623), Bug hunt ledger: uv #310 (Hosted uv rollback / remove ignore exclude-newer-package: on uv 0.12+ the restored uv.lock gains an sdist the per-package cutoff had excluded, so the restore isn't the original lock #1604, Hosted rollback / remove of a uv pip compile --no-build / --only-binary / --no-binary pylock.toml re-adds the artifacts uv filtered out (uv 0.9.16+), so the restore isn't the original lock #1613), Bug hunt ledger: Poetry #311 (Hosted and vendored rewrites replace poetry.lock with a file owned by the user running socket-patch, so after a root scan (e.g. a Docker bind mount) the lock's owner gets "Permission denied" from poetry add / poetry lock #1635), Bug hunt ledger: Pipenv #313 (Vendored PyPI wheels aren't checked against .gitignore or Git LFS rules (*.whl, .socket/), so a vendored Pipenv scan exits 0 and every fresh clone's pipenv sync fails #1572)
• 2026-10-21 13:22Z: removed agent:claimed from 11 closed issues (Vendored vlt scan accepts a package with a preprepare or postprepare script, which vlt ci then runs inside the committed vendor directory, so vendor --check and vex fail and repair loops #1633, Agent-mode npm apply, apply --check and vex skip a declared workspace member whose directory is named build, dist, vendor, tmp, temp or coverage, so its nested copy stays unpatched while VEX attests not_affected #1627, socket-patch --update on a Bun-installed copy says "managed by npm" and gives an npm command: npm update -g leaves a bun add -g install stale, and npm install …@latest in a Bun project breaks bun install --frozen-lockfile #1621, Hosted and vendored Pipenv refuse a patch whenever another Pipfile.lock category pins a different release of the package, so the category that pins the patched release stays unpatched #1616, Yarn berry treats a portal:/link:/file: copy whose package.json has an empty or invalid name ("" or "../x") as a different package, so scans succeed and VEX attests not_affected while that copy installs unpatched (#1579 follow-up) #1598, Hosted yarn classic refuses a patch that doesn't change dependencies when the registry metadata's ranges differ from the tarball's package.json (redirect_yarn_classic_dep_manifest_unlocked) #1578, Hosted uv scan gives no uv < 0.5.6 advisory for transitive overrides or repointed constraints, so on uv ≤ 0.5.4 a plain uv sync silently reinstalls the unpatched wheel after a clean exit 0 #1569, Lock-only yarn classic VEX wrongly omits a correctly pinned patch with dependency_not_installed when the patched package.json has a "" range or a dependency yarn de-duplicates (regression from #1548) #1558, Root scan --mode vendored still exits 1 forever and drops its in-run VEX when a nested npm project has no lockfile (package-lock=false); the #1534 fix only covers nested projects with their own lock #1554, Hosted cargo redirect writes a sparse+ registry even when the project declares rust-version < 1.68, so every build on that cargo fails with "usage of sparse registries requires -Z sparse-registry" while scan reports success #653, Vendored cargo warns cargo_multi_version_old_cargo ("declares no rust-version") when the root package inherits rust-version from [workspace.package] #651)
• 2026-10-21 13:22Z: posted drift comments on ledgers Bug hunt ledger: npm #302 (Agent-mode npm apply, apply --check and vex skip a declared workspace member whose directory is named build, dist, vendor, tmp, temp or coverage, so its nested copy stays unpatched while VEX attests not_affected #1627, Root scan --mode vendored still exits 1 forever and drops its in-run VEX when a nested npm project has no lockfile (package-lock=false); the #1534 fix only covers nested projects with their own lock #1554), Bug hunt ledger: Yarn classic (1.x) #304 (Lock-only yarn classic VEX wrongly omits a correctly pinned patch with dependency_not_installed when the patched package.json has a "" range or a dependency yarn de-duplicates (regression from #1548) #1558, Hosted yarn classic refuses a patch that doesn't change dependencies when the registry metadata's ranges differ from the tarball's package.json (redirect_yarn_classic_dep_manifest_unlocked) #1578), Bug hunt ledger: Yarn Berry (2+) #305 (Yarn berry treats a portal:/link:/file: copy whose package.json has an empty or invalid name ("" or "../x") as a different package, so scans succeed and VEX attests not_affected while that copy installs unpatched (#1579 follow-up) #1598), Bug hunt ledger: Bun #306 (socket-patch --update on a Bun-installed copy says "managed by npm" and gives an npm command: npm update -g leaves a bun add -g install stale, and npm install …@latest in a Bun project breaks bun install --frozen-lockfile #1621), Bug hunt ledger: vlt #307 (Vendored vlt scan accepts a package with a preprepare or postprepare script, which vlt ci then runs inside the committed vendor directory, so vendor --check and vex fail and repair loops #1633), Bug hunt ledger: uv #310 (Hosted uv scan gives no uv < 0.5.6 advisory for transitive overrides or repointed constraints, so on uv ≤ 0.5.4 a plain uv sync silently reinstalls the unpatched wheel after a clean exit 0 #1569), Bug hunt ledger: Pipenv #313 (Hosted and vendored Pipenv refuse a patch whenever another Pipfile.lock category pins a different release of the package, so the category that pins the patched release stays unpatched #1616), Bug hunt ledger: Cargo #315 (Vendored cargo warns cargo_multi_version_old_cargo ("declares no rust-version") when the root package inherits rust-version from [workspace.package] #651, Hosted cargo redirect writes a sparse+ registry even when the project declares rust-version < 1.68, so every build on that cargo fails with "usage of sparse registries requires -Z sparse-registry" while scan reports success #653)
• 2026-10-17 13:20Z: posted a drift comment on ledger Bug hunt ledger: Yarn classic (1.x) #304 (to-do item 0000000000 still pending on Yarn classic VEX still attests a pre-v5 hosted pin that yarn installs without the patched package's dependencies: #1463 checks only that the dependency's name is installed, and lock-only vex doesn't check at all #1538, fixed by Fix yarn classic VEX for unlocked dep ranges (#1538) #1548 on 2026-10-14)
• 2026-10-16 13:23Z: released stale claim 2026-10-13T14:22:13Z-3898b9 on Slow scan: poetry hosted 2.6x median ms/pkg (lock_fragments::rewrite_batch + VEX lock re-parse) #1473 (slices Fix slow hosted Poetry lock rewrite (#1473) #1475 and Read Python locks without copying them in VEX (#1473) #1486 merged, no open PR, claimer silent >48h; kept open because the bench ledger still lists poetry slow at 2.37x on 10-15 and 2.67x on 10-16)
• 2026-10-16 13:23Z: removed agent:claimed from 8 closed issues (Yarn berry still drops a portal: copy whose target has no package.json (e.g. a .gitkeep placeholder) or whose package.json lacks name/version, so scans succeed and VEX attests not_affected while that copy installs unpatched #1579, VEX gemspec product detection reads commented-out # spec.name = / # spec.version = lines, so the document names the wrong product or version #1573, vlt 1.4.0 reads workspaces from pnpm-workspace.yaml, so the #942 / #1134 member refusals miss those members: hosted and vendored scans write a stray member lock and exit 0, and vendored VEX attests not_affected #1564, Yarn berry drops a relative portal: / link: copy whose target directory is missing (e.g. an uninitialized git submodule), so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1561, Hosted pnpm 11/12 scan treats an empty (or null/undefined) pnpm_config_trust_lockfile as false and skips the trustLockfile config, so the next frozen install fails #1557, Vendored PyPI wiring isn't treated as contested when Pipfile.lock (or requirements.txt) points the same release at a non-Socket file/URL/path, so vendor --check stays green and vex attests not_affected while pipenv sync installs upstream #1549, VEX product purl detected from pyproject.toml keeps the raw project name (pkg:pypi/My_Service) instead of the normalized pypi name #1547, uv project under a parent uv.toml / [tool.uv]: hosted and vendored scan add a [tool.uv] table to the project's pyproject.toml, which hides the parent settings from uv, so uv sync --locked fails and a plain uv lock re-resolves without them #1545)
• 2026-10-16 13:23Z: posted a drift comment on Benchmark progress: socket-patch scan #575 (bench runs 2026-10-12 to 2026-10-16 are on bench/ledger but not in the discussion)
• 2026-10-15 13:26Z: closed NuGet version identity is normalized by vendor but not by PurlKey, so a freshly vendored 4-part version is judged unused and pruned #1202 as completed (Key NuGet purls by the normalized version in PurlKey (#1202) #1230 8439e555 and Look up NuGet packages by normalized version in the crawler (#1202) #1239 d240c658; PurlKey and the crawler normalize NuGet versions, and nuget_vendored_at_a_four_part_version_stays_live covers the prune case; only an optional file move is left)
• 2026-10-15 13:26Z: closed Hash agent-mode jar members through the shared streaming zip comparator instead of buffering each member #914 as completed (Stream agent-mode jar members through one zip-member hasher (#914) #1253 e9be7462; verify_member_bytes streams via zip_member_git_sha256, regression test verify_member_bytes_streams_a_large_deflated_member)
• 2026-10-15 13:26Z: removed agent:claimed from 38 closed issues (Hosted and vendored scans from a vlt workspace member with a stray vlt-lock.json still write to that lock and exit 0 when the root's workspaces glob uses an extglob (packages/+(a|b), packages/@(a|b)); vendored VEX then attests not_affected #1542, Vendored Bun tarballs go into Git LFS when .gitattributes tracks *.tgz with LFS, so a checkout without LFS fails bun install --frozen-lockfile #1541, Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540, Yarn classic VEX still attests a pre-v5 hosted pin that yarn installs without the patched package's dependencies: #1463 checks only that the dependency's name is installed, and lock-only vex doesn't check at all #1538, Root scan --mode vendored exits 1 forever and drops its in-run VEX when a nested independent npm project installs a patched package the root lock doesn't have (hosted mode only warns) #1534, Hosted gem rollback / remove strip the DEPENDENCIES ! when the user's source … do block opens after a ; on the same line, so frozen installs fail on Bundler 4.0.19+ #1531, Hosted pnpm 11/12 scan ignores a pnpm_config_trust_lockfile=false env override and says "installs need no extra flags", but the next frozen install fails with ERR_PNPM_TARBALL_URL_MISMATCH #1514, Hosted and vendored Poetry rewrites break poetry install on Poetry 1.4–2.2 when the patched dependency is declared with source = "pypi" ("Repository \"pypi\" does not exist."), with no warning #1282, Path-scoped agent scan packages/a and rollback packages/a skip a workspace member's npm alias (lp@npm:left-pad) under install-strategy=linked, while its plain links are in scope (exit 0, success) #1266, Yarn classic hosted and vendored scans miss a file: directory copy of the patched package declared under another dependency name, so scan --vex and lock-only vex attest not_affected while that copy installs unpatched #1236, Upstream restore sends every public-registry lookup at once; the registry_concurrency cap has no caller #1220, Hosted npm scan appends allow-remote=all to a CRLF .npmrc with no final newline as "\nallow-remote=all\r", leaving an LF line and a bare-CR ending that socket-patch's own .npmrc planner refuses #1196, Vendored bun.lockb workspaces write the member-relative tarball mirrors with no .gitignore check, so a *.tgz rule drops them from the commit and fresh frozen installs fail (Bun 1.1.39–1.2.23) or hang (1.3.9) #1116, Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100, Hosted scan from a yarn classic workspace member still pins nothing and exits 0 when the root's workspaces use a ! pattern (yarn 1 ignores it) or an extglob like packages/@(a|b) #1097, Hosted pnpm scan pins a pnpm-lock.yaml that pnpm is configured to ignore (lockfile=false / lockfile: false), reports success, and lock-only VEX attests not_affected while pnpm installs the upstream package #1074, Vendored gem revert restores Gemfile.lock but leaves the Gemfile path: line when that line carries a trailing comment, and no re-run can finish it #988, Gem agent crawl ignores that BUNDLE_GEMFILE=gemfiles/x.gemfile moves Bundler.root, so a relative bundle path resolves to the wrong dir, apply patches the system copy and vex attests not_affected while Bundler loads the unpatched gemfiles/vendor/bundle copy #952, Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939, Vendored uv script lock: after the user changes the vendored package's specifier in the PEP 723 block, vendor --revert / remove / rollback write the stale ==1.16.0 back into <script>.py.lock, so uv run --locked fails (exit 0) #869, Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759, VEX product detection ignores PDM 0.x's [tool.pdm] name/version, so vex and scan --vex fail with product_undetected on PDM 0.12 projects (after scan has already rewritten pdm.lock) #642, Composer global-home fallback checks ~/.composer before the XDG home, so scan -g finds no Composer 2 global packages when a stale ~/.composer exists and composer isn't on PATH #586, Hosted and vendored uv wiring ignore no-sources = true: scan and vendor report success, uv sync --locked then fails, and a plain uv sync reinstalls the unpatched wheel #564, Vendored Hatch wiring makes every Hatch install fail when the checkout path contains %XX, # or ; (e.g. a Jenkins "feature%2Fx" workspace), because Hatch's {root:uri} only escapes spaces #547, Running Go apply in a second go.work member writes a second replace for the same module@version, so every workspace build fails with "conflicting replacements" while apply, apply --check and VEX all report success #531, Hosted Go redirect's not_in_module_graph gate counts a go.sum /go.mod-only line as "in the graph", so on a go 1.16 module it writes an inert replace for an unselected version and VEX attests not_affected #509, Agent-mode Go vex omits an applied patch for a +incompatible module (not_applied, exit 1) because it looks up the manifest with a literal "+" while the API key spells it %2B #484, Go apply writes its replace into a root go.mod that go.work doesn't use, so the workspace build links the unpatched module while apply, apply --check and VEX all report it patched #458, Hosted cargo scan in a cargo vendor project reports success but breaks every fresh cargo build --frozen --offline, and VEX then omits the patch #455, Composer crawler ignores a vendor-dir set in the global Composer config, so scan -g and agent scans report "No packages found" and leave installs unpatched #439, In a --system-site-packages venv, pip keeps the base interpreter's unpatched copy after a hosted rewrite, no stale-install warning fires, and vex attests it as patched #409, A user replace in go.work silently overrides the Socket go.mod replace: Go apply and vendor report success and VEX attests not_affected while the build links the user's target #393, Agent-mode Go apply writes a go-patches replace for a module version the build graph doesn't select, reports it applied, and on a go 1.16 go.mod apply --check and vex also report it as patched #392, Agent-mode Go vex attests not_affected after go get upgrades the patched module, although the go-patches replace no longer applies and the build links the unpatched code #391, Hosted cargo redirect refuses a crates.io dependency declared with an explicit registry = "crates-io", treating crates.io as "another registry" #386, Agent-mode cargo apply patches only the first of several registry/src index dirs (cargo 1.84 vs 1.85+ hashes), so one cargo keeps building the unpatched crate while apply and VEX report success #339, Agent-mode cargo apply patches the wrong copy when cargo vendor uses a custom directory (or apply runs from a workspace member), yet reports success and VEX attests not_affected #338)
• 2026-10-15 13:26Z: posted drift comments on ledgers Bug hunt ledger: Bun #306 (Vendored Bun tarballs go into Git LFS when .gitattributes tracks *.tgz with LFS, so a checkout without LFS fails bun install --frozen-lockfile #1541) and Bug hunt ledger: pnpm #303 (Hosted pnpm 11/12 scan ignores a pnpm_config_trust_lockfile=false env override and says "installs need no extra flags", but the next frozen install fails with ERR_PNPM_TARBALL_URL_MISMATCH #1514 still fail in the 11.28.3 / 12.11.2 rows)
• 2026-10-14 13:21Z: removed agent:claimed from 22 closed issues (VEX product detection fails on Poetry 2 projects that declare dynamic = ["version"] with the version in [tool.poetry], so scan --vex exits 1 after rewriting poetry.lock #1527, Vendored requirements.txt can't be reverted or removed once a later scan also wires a pylock.toml: the entry flips to flavor python-lock, whose revert calls its own requirements_line wiring "unexpected" drift (exit 0, nothing restored) #1524, Bun 1.3.0 and 1.3.1 locks have no configVersion, so a "!"-excluded member is still refused in hosted and vendored mode after the #1492 fix (regression since #1480) #1521, Yarn classic renamed-copy detection (#1489) misses a file: copy outside the project root and a tarball whose root isn't package/, so scans succeed and VEX attests while that copy installs unpatched #1516, Vendored npm vex and scan --mode vendored --vex attest not_affected beside a file: directory copy of the patched name@version, which npm installs unpatched #1511, Hosted gem rollback / remove strip the DEPENDENCIES ! when the user's source block opener spans lines or uses braces, so frozen installs fail on Bundler 4.0.19+ #1509, Pipenv base-interpreter remedy (#1450) prints pipenv requirements --categories "packages docs", which Pipenv 2022.12.x–2023.2.4 export as empty, so following it installs nothing (exit 0) #1507, Poetry source-pin guard lets hosted and vendored rewrite a lock-version 1.1 poetry.lock that no Poetry 2.x can install, and the advisory says 2.3+ install it #1503, uv PEP 723 script in a subdirectory: hosted and vendored wiring ignore no-sources = true from a parent uv.toml / pyproject.toml, so uv run --locked fails and a plain uv run imports the unpatched package #1501, Agent-mode scan run from a vlt (or pnpm) workspace member fails package_not_installed for the member's npm-alias dependency, while the same alias patches from the root #1494, Bun 1.3+ bun.lockb root is read as pre-1.3, so a "!"-excluded member can't be patched in hosted or vendored mode (regression in 5.0.1) #1492, Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490, Hosted npm scan --vex attests not_affected when the lock also installs the same name@version from a file: tarball or directory, which npm installs unpatched (tarball shape regressed in #1008) #1481, Hosted gem scan ignores a Gemfile lockfile "custom.lock" DSL call (Bundler 4), so it pins the unused Gemfile.lock, leaves the real lock untouched, and every frozen install fails #1477, Hosted gem rollback / remove still strip the DEPENDENCIES ! when the user's source … do block holds an assignment-form v = if/case/begin … end, so frozen installs fail on Bundler 4.0.19+ #1476, Perf regression: hatch/hosted wall +21% (9c43dfc9..17793173) #1471, vendor --check reports a missing or corrupt vendored artifact as a raw Rust Debug value (Corrupt { reason: "vendor_workspace_artifact_missing" }) with no remedy, though socket-patch repair fixes it #1467, Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465, Hosted yarn classic rescan and VEX accept a pin written by v4.0.0 whose patched package.json adds a dependency the lock doesn't have, so yarn installs the patched package without it #1462, Hosted pnpm scan refuses with redirect_pnpm_lockfile_disabled over env lockfile settings the project's pnpm major ignores (e.g. any pnpm 11/12 project run through npm exec with package-lock=false) #1460, Pipenv stale-install remedy can't replace a base-interpreter copy in a --site-packages venv: pip uninstall refuses it and pipenv sync keeps it, so following the warning leaves the package unpatched #1450, Hosted uv: after uv remove <parent> or uv lock --upgrade-package <parent> drops a hosted-pinned transitive package, its leftover override makes rollback, remove and list fail forever with hosted_wiring_contested #1445)
• 2026-10-14 13:21Z: posted drift comments on ledgers Bug hunt ledger: pnpm #303 (Hosted pnpm scan refuses with redirect_pnpm_lockfile_disabled over env lockfile settings the project's pnpm major ignores (e.g. any pnpm 11/12 project run through npm exec with package-lock=false) #1460), Bug hunt ledger: Yarn classic (1.x) #304 (Hosted yarn classic rescan and VEX accept a pin written by v4.0.0 whose patched package.json adds a dependency the lock doesn't have, so yarn installs the patched package without it #1462, Yarn classic renamed-copy detection (#1489) misses a file: copy outside the project root and a tarball whose root isn't package/, so scans succeed and VEX attests while that copy installs unpatched #1516), Bug hunt ledger: Bun #306 (Bun 1.3.0 and 1.3.1 locks have no configVersion, so a "!"-excluded member is still refused in hosted and vendored mode after the #1492 fix (regression since #1480) #1521), Bug hunt ledger: uv #310 (Hosted uv: after uv remove <parent> or uv lock --upgrade-package <parent> drops a hosted-pinned transitive package, its leftover override makes rollback, remove and list fail forever with hosted_wiring_contested #1445, uv PEP 723 script in a subdirectory: hosted and vendored wiring ignore no-sources = true from a parent uv.toml / pyproject.toml, so uv run --locked fails and a plain uv run imports the unpatched package #1501), Bug hunt ledger: Poetry #311 (Poetry source-pin guard lets hosted and vendored rewrite a lock-version 1.1 poetry.lock that no Poetry 2.x can install, and the advisory says 2.3+ install it #1503, VEX product detection fails on Poetry 2 projects that declare dynamic = ["version"] with the version in [tool.poetry], so scan --vex exits 1 after rewriting poetry.lock #1527), Bug hunt ledger: Bundler (RubyGems) #316 (Hosted gem rollback / remove still strip the DEPENDENCIES ! when the user's source … do block holds an assignment-form v = if/case/begin … end, so frozen installs fail on Bundler 4.0.19+ #1476, Hosted gem scan ignores a Gemfile lockfile "custom.lock" DSL call (Bundler 4), so it pins the unused Gemfile.lock, leaves the real lock untouched, and every frozen install fails #1477, Hosted gem rollback / remove strip the DEPENDENCIES ! when the user's source block opener spans lines or uses braces, so frozen installs fail on Bundler 4.0.19+ #1509)
• 2026-10-13 13:25Z: released stale claim 2026-10-08T17:56:10Z-d68635 on Tracking: build and classify purls through one validated utils::purl API #748 (slices Compare purls through one PurlKey type #1045 and Guard single-segment name/version coordinates through one path_safety check (#748) #1153 merged 2026-10-08, no open PR, claimer silent since 2026-10-08 18:00Z)
• 2026-10-13 13:25Z: released stale claim 2026-10-08T10:59:14Z-aa074d on Route purl ecosystem checks through Ecosystem::from_purl instead of 24 inline starts_with("pkg:<type>/") tests #747 (Classify purls through Ecosystem::from_purl in free files (#747) #1126 merged slice 1 on 2026-10-11 01:02Z; about 68 inline starts_with("pkg:<type>/") checks remain on main, no open PR)
• 2026-10-13 13:25Z: removed agent:claimed from 4 closed issues (A bare scan or get on a project holding both vendored packages and hosted pins silently converts every hosted pin to vendored (exit 0, no warning), so it undoes a partial hosted takeover #1437, Hosted yarn berry rollback/remove put back a descriptor that yarn remove deleted from one workspace member, so every yarn install --immutable fails YN0028 #1435, Perf regression: yarn-classic/hosted wall +165% (5096c41a, #1328) #1423, CI perf: full tier (41 legs) runs on every push to main, not just nightly #1414)
• 2026-10-12 13:35Z: released stale claims on Yarn classic hosted and vendored scans miss a file: directory copy of the patched package declared under another dependency name, so scan --vex and lock-only vex attest not_affected while that copy installs unpatched #1236 (2026-10-09T07:22:27Z-55af4e), NuGet version identity is normalized by vendor but not by PurlKey, so a freshly vendored 4-part version is judged unused and pruned #1202 (…-4b9e1c), Tracking: assert stable codes instead of human sentences in CLI tests, and fold the covgap suites #1089 (…-6bbcee), Tracking: revert every vendored backend through one record-revert engine instead of nine hand-written mechanisms #989 (…-4f66ea), Consolidate remaining BOM stripping after the pnpm reader failures were fixed #905 (…-7070bc), Pick the line terminator for spliced lines through one line_endings::terminator #815 (…-78dc6b), Delete the vendored and hosted-vlt helpers left without a production caller by the v5 consolidation #782 (…-4b7e1a), Read and splice nuget.config through formats::nuget in hosted, vendored and restore #594 (…-ead28c): slices merged by 2026-10-09 23:08Z, no open PR for the rest, claimer silent for more than 48h
• 2026-10-12 13:35Z: removed agent:claimed from 11 closed issues (CI perf: e2e-build-windows — full Windows test build is the merge-queue critical path in 27/30 runs (~2.5 min off every merge) #1385, Yarn classic: vendor --check / repair pass a yarn.lock with a dangling dependency descriptor written by a pre-v5 release #1379, Vendored uv transitive package later added as a direct dependency (uv add six==1.16.0): vendor --revert / remove / rollback half-revert the pair, so uv sync --locked fails and vendor --check claims nothing references the wheel #1374, CI perf: PR CI — 23% of full PR runs re-test unchanged diffs after a merge-main push (~20–30k Linux job-min/day, feeds the ubuntu-latest backlog) #1373, Vendored mode leaves a Pipenv-written pylock.toml or a uv-export requirements.txt unpatched beside the wired lock #1368, Vendored uv script locks: after uv remove --script drops the package from one of two vendored scripts, every unwind keeps the other script wired (revert exits 0, remove/rollback exit 1, hosted takeover refuses) #1285, The #812 replace-registry-host warning misses a ${VAR} value in .npmrc: npm expands it to always, so every npm ci fails E404, while the hosted scan reports success with no warning #1233, Gem agent apply patches only the ruby-platform x-1.0/ dir when a x-1.0-x86_64-linux-gnu/ sibling is also installed, so Bundler loads the unpatched platform gem while vex attests not_affected #1092, Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082, Gem BUNDLE_GEMFILE check compares paths lexically, so a symlinked spelling of the project's own Gemfile (e.g. macOS /tmp/app/Gemfile) is refused, and vex / rollback reject the hosted patch Bundler is loading #896, Vendored uv script locks: once the user deletes one wired script (or its .py.lock), vendor --revert, remove, rollback and the hosted takeover can never unwind the other scripts, and the takeover's suggested fix is the command that fails #890)
• 2026-10-12 13:35Z: posted drift comments on ledgers Bug hunt ledger: npm #302 (The #812 replace-registry-host warning misses a ${VAR} value in .npmrc: npm expands it to always, so every npm ci fails E404, while the hosted scan reports success with no warning #1233), Bug hunt ledger: Yarn Berry (2+) #305 (Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082), Bug hunt ledger: uv #310 (Vendored uv script locks: after uv remove --script drops the package from one of two vendored scripts, every unwind keeps the other script wired (revert exits 0, remove/rollback exit 1, hosted takeover refuses) #1285), Bug hunt ledger: Bundler (RubyGems) #316 (Gem BUNDLE_GEMFILE check compares paths lexically, so a symlinked spelling of the project's own Gemfile (e.g. macOS /tmp/app/Gemfile) is refused, and vex / rollback reject the hosted patch Bundler is loading #896, Gem agent apply patches only the ruby-platform x-1.0/ dir when a x-1.0-x86_64-linux-gnu/ sibling is also installed, so Bundler loads the unpatched platform gem while vex attests not_affected #1092)
• 2026-10-11 13:26Z: released stale claim 2026-10-08T02:56:01Z-9ee976 on Route the remaining hand-rolled child-process deadlines through utils::process #1067 (Bound the PDM site probe through utils::process (#1067) #1106 merged the pdm_site slice only, claimer silent since 2026-10-08 03:01Z)
• 2026-10-11 13:26Z: released stale claim 2026-10-08T15:55:44Z-d66405 on Tracking: read and edit pom.xml through one element scanner in formats::maven #715 (Read Gradle verification metadata through one shared XML scanner (#715) #1145 merged item 6 only, claimer silent since 2026-10-08 16:02Z)
• 2026-10-11 13:26Z: released stale claims on Tracking: drive the seven npm-family vendor backends through one generic driver #920 (Fix open npm issues #1008 merged as "Part of") and Benchmark tracking: socket-patch scan #580 (Stop re-parsing bun lock entries for every patch in scan (#580) #1051 merged, tracker kept open); neither had a Claim-ID, both silent for more than 48h
• 2026-10-11 13:26Z: removed agent:claimed from 134 closed issues (Hosted NuGet remove / rollback / takeover restore packages.lock.json to the nuget.org catalog packageHash, which isn't NuGet's contentHash for signed packages, so every later dotnet restore fails NU1403 #624, Decide: warn on and then remove scan --apply/--vendor, and whether --vex stays embedded #966, Yarn classic: a patch that adds a dependency to the package's own package.json leaves vendored yarn.lock with a dangling dependency (offline frozen install fails, lock churns), and hosted silently installs without it #591, Maven pom rewrites add a second <repositories> or <dependencyManagement> section when the existing one is self-closed or has a comment before <dependencies>, so Maven refuses the pom #342, Vendored and hosted NuGet patches are shadowed by a warm global packages folder: silently unpatched without a lock, NU1403 with one #352, Hosted Maven rewriter ignores <classifier> and suffixes sources/tests/native classifier dependencies, which breaks the build #262, Hosted Maven rewriter edits commented-out, plugin and profile markup, so builds either stay unpatched or break #259, Hosted/vendored NuGet mapping isn't exclusive when nuget.config already maps the exact package id to another source, so restore races the Socket feed against nuget.org (NU1403 with a lock, silently unpatched without one) #462, NuGet nuget.config authored by vendored/hosted mode maps '*' only to nuget.org, cutting off sources inherited from parent or user-level configs (NU1101) #354, With --manifest-path into another project, rollback, remove, repair, vex, scan and get read the vendored ledger from --cwd #745, Vendored mode in a Pipenv project wires only Pipfile.lock and silently leaves a sibling requirements.txt unpatched, and the hosted → vendored takeover reverts that file's hosted pin to plain PyPI #612, Go apply and vendor wire in a patched module whose go.mod raises or adds a requirement without syncing the consumer go.mod/go.sum, so every default go build fails while apply, --check and VEX report success #618, Go apply and vendor break every build in projects with a committed vendor/ directory (modules.txt not synced), while apply --check and VEX report success #343, Maven hosted scan pins, and VEX attests, artifacts the project doesn't depend on (the crawler lists all of ~/.m2) #265, Vendored NuGet on a core.autocrlf checkout: vendor --revert / remove / rollback revert packages.lock.json but leave nuget.config wired, so every restore fails NU1403 (vendor --revert exits 0) #537, Vendored Maven, Gradle and NuGet artifacts can be git-ignored silently, because only npm checks .gitignore #1061, Hosted PDM rollback and remove replace a private index's static_urls with files.pythonhosted.org, so PDM bypasses the mirror (or fails on 2.12 behind a firewall) #413, Agent-mode cargo scan --sync / --prune drops the manifest entry of a crate the lock no longer resolves but leaves its shared registry-cache copy patched, so rollback can't restore it (regression from #1205) #1278, Cargo rollback after an agent→vendored takeover leaves the shared registry cache patched, reports success, and deletes the revert blobs #336, Hosted gem rollback / remove strips the DEPENDENCIES ! of a gem the user declared inside a source "https://rubygems.org" do block, so every frozen install fails after the unwind #1056, Vendored and hosted NuGet ignore a per-project packages.<project>.lock.json, so the lock is never re-pinned and every later restore fails NU1403 while VEX attests the patch #514, Agent-mode cargo apply/rollback has no effect on an already-built project: cargo reuses the cached rlib from target/, while apply reports success and VEX attests not_affected #387, Vendored and hosted NuGet leave member-project packages.lock.json unpinned in a solution layout, so every fresh restore fails NU1403 #353, remove and rollback call a vendored PyPI residual-reference keep "lockfile wiring drifted", and their "re-run scan --mode vendored to normalize, then remove" remedy loops (Pipenv pipenv requirements export) #1184, After a hosted or vendored PDM rollback, pdm sync / pdm install keep the patched build installed, though rollback says the next install restores it #477, Hosted cargo scan redirects a crate the user overrides with [patch.crates-io], silently dropping the override and breaking --locked #480, Vendored pnpm 7–11 scan exits 1 after pnpm remove (or an upgrade) because it tries to vendor the orphaned node_modules/.pnpm/<name>@<ver> that pnpm keeps for 7 days, and the suggested pnpm install doesn't clear it #1197, Hosted and vendored pnpm scans add keys to an empty or comment-only pnpm-workspace.yaml without packages:, so every pnpm 8.x–10.4 command then fails with "packages field missing or empty" #1096, After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203, Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017, Hatch 1.17+ projects with a hatch-generated pylock.toml get only the lock rewritten, and Hatch regenerates it from pyproject, so hosted and vendored patches are silently dropped #479, uv projects that declare the patched package as a PEP 508 direct URL (six @ https://… / git+…): vendored writes a lock uv sync --locked rejects while vex attests, and hosted overrides the user's URL then refuses to roll it back #767, Lock-only requirements.txt discovery sends PEP 440-equivalent pins verbatim (six==1.16 → pkg:pypi/[email protected]), so a fresh checkout reports "No patches available" while the same file with a venv is patched #604, Hosted yarn classic rewrite drops the #sha1 fragment when the grant has no sha1, so yarn's cache serves stale bytes: yarn ≤1.17 silently installs the unpatched package, and yarn ≥1.19 fails every warm-cache install #558, On Windows, Go apply and vendor always fail with "Access is denied. (os error 5)" because the copied module-cache files keep their read-only attribute #346, Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131, Scan from a hatchling member of a uv workspace rewrites the member's pyproject.toml as a lockless Hatch project, so the root uv.lock goes stale, uv sync --frozen installs the unpatched release and vendored vex attests not_affected #1138, Vendored Maven reactor pins over an imported BOM or external parent, so a build that uses 1.11.0 is silently downgraded to 1.10.0-socket.* and a later BOM bump never takes effect #488, Vendored uv transitive package: after uv remove of its parent, scan --prune, vendor --revert, remove and rollback drift-keep it, so vendor --check stays red and its prune remedy loops (project and script lanes) #1287, v5 Bundler plugin cleanup leaves .bundle/plugin registered in every other checkout, so bundle install crashes with LoadError on Bundler 2.3–2.5 #1295, vendor --force documents a missing-file tolerance and a mismatch warning that no vendored backend implements #923, repair and scan --prune delete the beforeHash blobs of active patches, so a later offline rollback fails and tells the user to run repair #893, Composer reinstall hints always name vendor/<vendor>/<name>, so with a custom config.vendor-dir following them leaves the installed package unpatched #658, Hosted and vendored NuGet reject a packages.lock.json with a UTF-8 BOM that dotnet restores fine: hosted skips the redirect and exits 0 success, vendored fails apply_failed #623, Hosted NuGet rewrites packages.lock.json entries at other versions of the patched id #593, Go settings written with go env -w are ignored: GOPRIVATE modules are requested from proxy.golang.org, a GOPROXY mirror is bypassed, and a GOMODCACHE cache is not found #344, apply --check drift report tells you to run socket-patch apply without the -g / --global-prefix / --cwd it was given, so following it patches nothing and exits 0 #1219, socket-patch --update on a pnpm-installed copy says "managed by npm" and gives an npm command: npm update -g leaves a pnpm global install stale, and npm install …@latest in a pnpm project breaks the next pnpm install --frozen-lockfile #1111, Hosted cargo remove writes a duplicate cfg-if block into Cargo.lock when crates.io also locks the same crate@version, so cargo can no longer parse the lock while remove reports success #863, Hosted cargo vex attests not_affected while Cargo.lock also builds an unpatched crates.io copy of the same crate@version #679, Yarn berry vendored and hosted pins of native-addon packages (nan, bufferutil, utf-8-validate, node-addon-api) keep the registry entry's implicit node-gyp: "npm:latest" dependency, so vendored installs and hardened hosted installs fail YN0028 #737, Vendored scala-cli gate passes a version conflict when a Bloop project file is truncated or oversized #1270, Hosted gem scan of a Gemfile with no lock still pins shared-gem-home versions: gem "x", "~> 2.0" becomes the older patched "1.0.0", and a gem the project never declared is appended as a new dependency #1125, Decide: make the command model read-only scan plus fix/undo/sync, with mode taken from project state, and make "nothing to undo" exit 0 #1088, Hosted Maven mode edits only the root pom of a multi-module build, leaves child literals unpatched, and still attests VEX #261, pnpm node-linker=pnp with a modulesDir is refused as yarn Plug'n'Play, because the layout detector ignores the modulesDir the crawler honors #1129, Human scan --mode vendored --prune silently skips the vendored GC when no remaining package has a patch, so an npm uninstalled vendored entry is never reverted (exit 0), while --json reverts it and vendor --check keeps pointing at that same command #1127, Hosted uv rollback and remove delete a user-authored override-dependencies = ["<pkg>==<ver>"] pin that hosted mode never added #411, Decide: support tiers for bun.lockb writes, vendored pnpm 7/8 locks, vlt pre-1.0 locks and hosted Maven/Gradle #1156, Every HTTPS call fails behind a TLS-inspecting proxy because the clients trust only bundled webpki roots #1107, Cargo apply on a cold or pruned registry cache now exits 0 as "lockfile-only", then the next cargo build downloads and compiles the unpatched crate (regression from #555) #616, CLI_CONTRACT.md documents status paidRequired for get and scan, but get emits "paid_required" and scan never reports it #982, remove, rollback and get treat case-distinct packages as one: remove pkg:npm/jsonstream also removes JSONStream's patch #1292, Hosted Bun rollback/remove ignores a private scope set in ~/.npmrc or ~/.bunfig.toml: it looks the package up on the public registry, then fails or writes a "" slot with the public package's integrity (#992 fix reads only the project's files) #1276, After npm install <pkg>@<other version> moves a vendored npm package off its patched version, scan --prune, vendor --revert, remove and rollback all drift-keep it, so vendor --check stays red and every remedy it names loops #1155, Vendored Pipenv re-serializes the whole Pipfile.lock, so a non-ASCII lock is rewritten throughout and its revert is not byte-identical #1128, Decide: make --download-mode file the default and retire the diff download path #792, scan exits 1 in human output but 0 with --json when every patch query returns nothing #1062, Hosted requirements.txt rewrite replaces a user's own direct reference (six @ https://mirror/…/six-1.16.0-….whl, file:// fork) with the Socket PyPI build, and rollback then restores six==1.16.0 from PyPI, losing the original source #542, Yarn classic hosted and vendored modes can't see or patch a yarn.lock block whose key has an empty range (left-pad@: from "left-pad": ""), so a lock-only scan reports no vulnerable package and an installed scan leaves it unpatched #1271, Gem VEX judges an unused system gem-home copy when the project sets a Bundler path, so standalone vex never attests #1098, Hosted pin on a bun.lockb record that Bun shares with a bundled copy can't be unwound: list errors, and the vendored takeover fails (#1008's #828 fix covers the text bun.lock only) #1243, Vendored NuGet doesn't recognise a close tag with whitespace (</packageSources >, </packageSourceMapping >), so it appends a second section that NuGet ignores and every restore fails NU1100 / NU1403 while scan reports success and VEX attests #685, Vendored→hosted takeover on yarn classic un-patches a vendored npm: alias copy when a direct copy is pinned, instead of retracting the takeover #1158, Hosted yarn classic scan --vex attests not_affected when an npm: alias copy of the patched package was skipped, while standalone vex refuses the same lock #1081, A failed VEX write leaves a truncated OpenVEX document at the output path #1144, Hosted gem rollback / remove leave the patched .gem in the project's committed vendor/cache, so every later bundle install fails with mismatched checksums (exit 37) while the unwind reports success #1260, Vendored PyPI revert, remove, rollback and the hosted takeover delete the vendored wheel while a root uv export -o requirements.lock (Rye-style name) still installs from it (exit 0) #1252, After uv remove --script drops a vendored package from a PEP 723 script lock, scan --prune, vendor --revert, remove, rollback and the hosted takeover still drift-keep it, so vendor --check stays red and its prune remedy loops #1214, Scan of a fresh Poetry checkout (no Poetry env yet, default virtualenvs.create) crawls the system Python: vendored exits 1 on system-only packages and agent mode patches dpkg-owned files (the Poetry side of #947 / #964) #1023, With {data-dir} in Poetry's virtualenvs.path, agent mode also patches an unrelated activated VIRTUAL_ENV / conda env, even though poetry env use pins the project's env, and hosted VEX then refuses a correctly installed patch #866, With Poetry virtualenvs.create = false, agent mode patches a stray ./venv (or ./.venv under in-project = false) instead of the system env Poetry installed into, and VEX attests not_affected #671, Lock-only requirements.txt discovery drops a pin whose last line ends in a dangling \ continuation (six==1.16.0 \ at EOF): scan exits 0 with "No patches", but pip installs it #1249, Hosted and vendored scans from a vlt workspace member with a stray vlt-lock.json write to that lock, which vlt ignores, and exit 0 (vendored VEX then attests not_affected while vlt ci fails) #1134, Capped hosted scan (--max-new-patches 0) defers an already-pinned npm patch as NEW when a second lock entry of the same version is unpinned, so the vex remedy loops and that copy stays unpatched (regression from #1058) #1195, Hosted and vendored scans from a Bun workspace member with a stray bun.lock / bun.lockb pin that ignored lock, exit 0, and lock-only VEX attests not_affected while Bun installs the unpatched package #1101, On Bun ≥ 1.3.5, hosted and vendored rewiring drops Bun's default trust, so install scripts of patched packages (better-sqlite3, esbuild, sharp…) are silently blocked #371, Bun hosted and vendored modes skip a URL or file: tarball copy of the patched package without warning, and vendored vex attests not_affected (the #326 fix covers npm locks only) #497, Global mode misses every Bun global package when BUN_INSTALL_BIN or BUN_INSTALL_GLOBAL_DIR is set: scan -g reports success with nothing found, get -g / vex -g patch and attest nothing #443, Perf regression: bun/hosted wall +110% (1169ae68, #472) #578, With Bun's globalStore (Bun ≥ 1.3.14), agent mode patches and rolls back every other project sharing the store, and vex attests unpatched transitive copies as not_affected #635, With Bun's isolated linker, vex refuses every hosted patch as not_applied after the usual in-place bun install, because it checks orphaned node_modules/.bun registry entries that Bun never removes (regression from #496) #599, After a Bun rollback or vendor --revert, the advised bun install keeps the patched bytes installed on the hoisted linker (Bun reports "no changes") #764, Lock inventory ignores a bun.lockb that Bun installs from when bun.lock is a dangling symlink #735, Vendored re-run on an isolated-linker bun.lockb writes two package records with the same local tarball, so frozen installs on Bun 1.3.9/1.4.2 fail intermittently with EEXIST #861, After Bun migrates a vendored bun.lockb to bun.lock (bun install --save-text-lockfile), vendor --revert and rollback fail, and a superseding re-vendor drops the pre-vendor original so revert exits 0 with the project still vendored #784, Hosted Bun rollback/remove writes an empty registry slot that Bun < 1.3.7 resolves against npmjs, so custom-registry projects can't frozen-install after a revert #992, Hosted pnpm rollback/remove restores pnpm-lock.yaml from npmjs's version document instead of the project's .npmrc registry, so a mirror project loses its tarball: URL (cold frozen install 404s) or is moved to npmjs #919, Decide: where patch API calls go when a token is set but the org slug can't be resolved #648, Global agent mode on pnpm 12 (and 11 without the global virtual store) patches only one of the per-install copies of a package, reports success, and VEX attests not_affected #435, Vendored pnpm 12 with packageManager set: the two-document pnpm-lock.yaml makes vendor refuse, and vendor --revert, rollback and the hosted takeover half-revert the project and break frozen installs #466, Hosted scan with pnpm gitBranchLockfile pins the stale pnpm-lock.yaml and reports success, while pnpm installs unpatched bytes from pnpm-lock.<branch>.yaml #556, Hosted scan on a pnpm workspace with sharedWorkspaceLockfile: false ignores the per-package pnpm-lock.yaml files and reports success while redirecting nothing #492, Hosted scan on a Rush repo with pnpm 11/12 reports success, but rush install then fails with ERR_PNPM_TARBALL_URL_MISMATCH, or (pnpm 11.0.0) silently installs the upstream package #713, Agent-mode apply in a pnpm workspace reports each member-linked package twice, inflating the --json skipped count with duplicate already_patched events #633, Hosted scan on a Rush repo with subspaces never emits redirect_rush_repo_state_stale, so rush install fails on the shrinkwrap hash check with no warning #714, Agent-mode scan packages/<member> finds nothing in a pnpm workspace (exit 0), while rollback packages/<member> selects the same packages #778, Hosted and vendored modes create a packages: ['.'] pnpm-workspace.yaml that turns a single-package project into a workspace, so pnpm add <pkg> fails with ERR_PNPM_ADDING_TO_ROOT on pnpm 9.0–10.4 #734, Vendored pnpm: unwinding a vendored package whose dependency is also vendored clobbers the child's lock wiring — remove <parent> breaks frozen installs, the hosted takeover silently unpatches the child, and rollback fails forever #830, Vendored pnpm refuses a user exact-pin override (left-pad: 1.3.0) in pnpm-workspace.yaml with a misleading "does not match package.json" error, though the same pin in package.json is taken over #854, pnpm hosted-to-vendored scan/get dry-run previews success for a refused takeover #853, Hosted pnpm rollback/remove adds registry tarball: URLs the lock never had when lockfileIncludeTarballUrl sits in a settings file the installed pnpm ignores (workspace file on pnpm 9, .npmrc on pnpm 11/12) #902, Hosted and vendored scans rewrite a Pipenv project's pylock.toml to an archive entry that Pipenv 2026.4+ ignores, so pipenv sync silently installs the unpatched release from PyPI #912, Build npm-family vendor ledger entries through one constructor instead of seven literal VendorEntry blocks #922, Resolve VEX npm alias copies through the core resolver and delete vex_consumed's second alias walk #856, Walk package-lock entries once for inventory, vendored, hosted and restore #663, remove --preserve-state on a manifest-less hosted npm project silently restores the pin without the documented hosted_state_not_preservable note #433, Agent-mode scan ignores socket.yml includePaths / ignorePaths (and the built-in tests/ default) for nested npm projects, patching every nested project's node_modules #554, npm vendored refuses a registry package with vendor_workspace_member whenever a local file: directory (or workspace member) has the same name@version, and the hosted→vendored takeover then un-hosts it, leaving it unpatched #688, npm hosted and vendored modes rewrite a lock entry nested under a dependency that ships npm-shrinkwrap.json (hasShrinkwrap), so npm 7–11 install it unpatched while vendored VEX attests not_affected #753, Hosted npm scan pins a package that npm 12's native patchedDependencies also patches, so every later npm ci / npm install fails EPATCHFAILED (and vendored refuses the lockfileVersion 4 lock with wrong advice) #711, npm hosted pin next to a bundled copy can't be unwound: rollback/remove refuse it, and the vendored takeover skips the restore, so vendor --revert lands back on hosted and allow-remote=all stays #828, Hosted npm scan pins a hosted tarball URL that npm rewrites to the registry under replace-registry-host=always, so every npm ci / npm install then fails E404 while the scan reports success #812, Vendored npm vex and vendor --check fail after any npm 7–10 npm install on a lockfileVersion 2 lock, because npm drops resolved from the legacy mirror and #813 treats that as an unpatched npm 6 install (regression) #879, npm 12 never reads npm-shrinkwrap.json, so on a shrinkwrap-only project hosted and vendored scans rewrite a lock npm 12 ignores: scan succeeds with no warning, lockfile-only VEX attests not_affected, and npm install installs the unpatched package #899, Vendored npm refusal for a symlinked package-lock.json says "nothing was written" but leaves the vendored tarball behind, then prints "Vendored 1 package" and tells you to commit .socket/vendor/ #898, Project-mode NuGet agent scan patches, and VEX attests, packages the project doesn't depend on (the crawler lists the whole ~/.nuget/packages) #427, Delete go_sum_edit's oracle-only free functions and move the go.sum codec to formats #631, Agent-mode apply and rollback reject a manifest hash in uppercase hex that blob download accepts as valid #707, Decide: one shape for the --json top-level error (scan and get emit both a string and a {code, message} object) #704, Decide: keep .socket/apply.lock transient, or give the lock a file that never has to be deleted #808, Vendored requirements.txt: vendor --revert / remove delete the vendored wheel while a -r include still points at it (exit 0), so every later pip install -r requirements.txt fails #867, Read Cargo.toml package name and version through one shared toml_edit reader #693, Decide: give SOCKET_FORCE per-command names so forcing a self-update doesn't also force apply and vendor #615)
• 2026-10-11 13:26Z: posted drift comments on ledgers Bug hunt ledger: npm #302, Bug hunt ledger: pnpm #303, Bug hunt ledger: Yarn classic (1.x) #304, Bug hunt ledger: Yarn Berry (2+) #305, Bug hunt ledger: Bun #306, Bug hunt ledger: vlt #307, Bug hunt ledger: pip / requirements.txt #309, Bug hunt ledger: uv #310, Bug hunt ledger: Poetry #311, Bug hunt ledger: PDM #312, Bug hunt ledger: Pipenv #313, Bug hunt ledger: Hatch #314, Bug hunt ledger: Cargo #315, Bug hunt ledger: Bundler (RubyGems) #316, Bug hunt ledger: Go modules #317, Bug hunt ledger: Maven #318, Bug hunt ledger: NuGet / dotnet #320, Bug hunt ledger: Composer #321 (issues closed since 2026-10-09 13:00Z still listed as fail)
• 2026-10-11 13:26Z: posted a drift comment on Benchmark progress: socket-patch scan #575 (Perf regression: bun/hosted wall +110% (1169ae68, #472) #578 closed 2026-10-09 but still listed as "run 1/2")
• 2026-10-09 13:35Z: removed agent:claimed from 29 closed issues (Vendored Poetry wires a 2.x lock through two different splicers depending on its line endings #936, Vendored npm re-scan exits 1 ("Failed to vendor", "1 failed") on every run while a superseding patch's artifact is pending_build / build_failed / not_found, although the vendored older patch is intact; hosted skips the same upgrade with exit 0 #954, Vendored npm scan wires file: tarballs that npm ≥ 11.14 refuses under allow-file=root (transitive deps) or allow-file=none, so every npm ci fails EALLOWFILE while scan, vendor --check and vex report success with no warning #969, Decide: vendor single-module Maven poms through the suffixed-version jvm planner and retire the same-GAV <repository> wiring #973, Perf regression: npm/hosted wall +15% (2463257a..9c43dfc9) #993, Vendored uv: vendor --revert / remove / rollback delete the vendored wheel while a uv export-ed requirements.txt or pylock.toml still points at it (exit 0), so installs from the exported file fail #996, scan --mode agent --json and get --json overwrite a locally modified npm file without the documented content_mismatch_overwritten warning (not in the JSON, not on stderr) #1004, A rolled-back vendor eject prints "Vendored 1 package" and "Commit .socket/vendor/" with no eject_rolled_back warning, and --json still reports the rolled-back package as applied #1005, Hosted and vendored pnpm 11/12 refuse a standalone project nested under an unrelated pnpm-workspace.yaml (not in its packages: globs) as a "workspace member", and the suggested fix doesn't work (regression from #888) #1006, Vendored uv repair pairs a hashless pure wheel with another wheel's hash, because ledger recovery re-parses uv.lock with its own scanner #1079, On Bun's isolated linker, rollback/remove of a superseded agent record (#934) drops the record and its blobs while the orphaned node_modules/.bun/<pkg>@<ver> copy still holds the agent patch, and the advised bun install relinks it #1084, Lockfile discovery treats a requirements.txt -r include as a competing lock, so after a hosted rewrite vex attests nothing (exit 2) and rollback refuses (exit 1), although pip install -r requirements.txt installs the patched wheel #1086, Hosted and vendored scans run from an npm workspace member that has a stray package-lock.json of its own rewrite that lock, which npm ignores, and report success while npm installs the unpatched package and VEX attests not_affected #1094, Lock-only scans still drop a requirements.txt pip decodes through a PEP 263 coding line (latin-1): "No pypi packages found", exit 0, while the same project with a venv refuses candidate_file_unreadable #1119, Vendored uv: a UTF-16 requirements.txt beside uv.lock is read as absent, so vex attests not_affected and vendor --check passes while uv pip install -r requirements.txt installs the unpatched release #1120, Vendored scan of a Pipenv use_pylock = true project wires only pylock.toml, but Pipenv installs from Pipfile.lock, so pipenv sync / install --deploy install the unpatched release after a "success" run #1122, After bun remove of a vendored package in a bun.lockb project, scan --prune, vendor --revert and remove keep it as "drifted", so vendor --check stays red and its remedy loops #1132, Vendored Poetry never re-vendors to a superseding patch: re-scan exits 1 with pypi_poetry_source_already_exists, while --dry-run previews would_revendor, and the project keeps installing the old patch #1136, After uv remove of a vendored package, scan --prune, vendor --revert, remove and rollback all keep it as "drifted", so vendor --check stays red and its suggested scan --prune fix loops #1140, After pipenv uninstall of a vendored package from a named category on Pipenv 2022/2023, scan --prune, vendor --revert, remove and rollback keep it as "drifted", so vendor --check stays red and its scan --prune remedy loops #1142, Lock inventory pins cp311/pp310/py2 "-none-any" wheels as pure, while vendored, hosted and recovery refuse them #1150, Vendored PyPI revert, remove and the hosted takeover still delete the vendored wheel while a requirements file in a subdirectory (requirements/dev.txt, pip freeze > requirements/lock.txt) installs from it (exit 0), so that install then fails #1167, Hosted gem re-scan refreshes a patch-registry GEM remote in place without re-sorting the lock's GEM sections, so after a superseding patch on a two-gem project every Bundler 4.0.19+ frozen install fails #1186, Scope the project-mode cargo crawl to the registry crates Cargo.lock resolves #1204, Scope the project-mode Go crawl to the modules go.sum records #1207, Since #1152, a plain-ASCII requirements.txt whose coding line names an unmodelled codec (iso-8859-15, cp1250, gbk…) is read as absent: scan finds nothing (exit 0), and vex / rollback can't see an existing hosted pin #1212, Vendored PyPI revert, remove, rollback and the hosted takeover still delete the vendored wheel while a uv export --format pylock.toml in a subdirectory installs from it (exit 0) #1213, Scope the project-mode Deno crawl to the JSR packages deno.lock records #1216, Capped hosted gem re-scan counts a Gemfile-only (no-CHECKSUMS) pin as NEW, so --max-new-patches N spends its budget on gems it already wired and starves the next one forever (regression from #1058) #1224)
• 2026-10-09 13:35Z: posted drift comments on ledgers Bug hunt ledger: npm #302, Bug hunt ledger: Yarn classic (1.x) #304, Bug hunt ledger: Bun #306, Bug hunt ledger: pip / requirements.txt #309, Bug hunt ledger: uv #310, Bug hunt ledger: Poetry #311, Bug hunt ledger: Pipenv #313, Bug hunt ledger: Cargo #315, Bug hunt ledger: Bundler (RubyGems) #316 and Bug hunt ledger: NuGet / dotnet #320 (closed issues still listed as fail)
• 2026-10-08 13:25Z: removed agent:claimed from 37 closed issues (Hosted Hatch rewrite leaves an existing Hatch environment unpatched with no stale-install warning, and vex still attests not_affected #335, Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539, Hosted yarn berry rewrites a mixed-line-ending package.json that vendored mode refuses #628, Share the yarn berry project gates between hosted and vendored modes #629, Hatch never picks up a superseding patch: re-scan refuses its own earlier wiring ("existing direct source must be reverted"), so hosted exits 0 still pinned to the old patch uuid #650, Vendor-service retries ignore an HTTP-date Retry-After: fold the vendor Retry-After parser and jitter onto api::retry #677, Compute sha256, sha1 and sha512-SRI digests through utils::digest instead of inline copies #706, Hosted and lock-only scans treat a UTF-16 requirements.txt (what Windows PowerShell's pip freeze > writes) as absent: exit 0, no warning, and pip keeps installing the unpatched pin #721, #723, #729, #742, #749, #751, #775, #832, #872, #903, #904, #907, #933, #938, #942, #945, #951, #958, #964, #967, #975, #979, #1001, #1013, #1024, #1028, #1048, #1055, #1071, #1078)
• 2026-10-08 13:25Z: released the stale claim 2026-10-06T13:22:24Z-2c1fea on #935 and #939 (PR #940 merged as Refs with the VEX half only, no follow-up PR, claimer silent for more than 48h)
• 2026-10-08 13:25Z: posted drift comments on ledgers #302, #303, #304, #305, #307, #310, #311, #314, #315, #316, #317 and #321 (issues closed since 2026-10-07 13:30Z still listed as fail)
• 2026-10-07 13:30Z: released the stale claim 2026-10-05T11:56:39Z-93d7a1 on #823 (#850 merged slice 1 only, no follow-up PR, claimer silent for more than 48h)
• 2026-10-07 13:30Z: removed agent:claimed from 33 closed issues (closed by the 2026-10-07 11:48–12:40Z merge wave, plus #364, #367, #410, #424, #464, #504 and #521, which were closed earlier)
• 2026-10-07 13:30Z: posted drift comments on ledgers #302, #303, #305, #306, #307, #309, #310, #313, #316 and #318 (issues closed 2026-10-07 still listed as fail)
• 2026-10-07 13:30Z: posted a drift comment on #575 (#760 and #762 are closed by #877 but still listed as slow)
• 2026-10-06 13:26Z: closed #417 as completed (PR #598 abb5787a said "Fixes #590 and #417", but only #590 auto-closed; cargo_hosted_scan_from_workspace_member_refuses on main)
• 2026-10-06 13:26Z: closed #585 as completed (PR #597 0c1e07b8 said "Fixes #561 and #585", but only #561 auto-closed; hosted NuGet anchors come from formats::nuget::parse_config)
• 2026-10-06 13:26Z: closed #264 as completed (PR #646 0685ba8c added patch/jvm_jar.rs, a member-keyed Maven record jar swap in apply_maven_base; tests in gradle_agent_cli.rs)
• 2026-10-06 13:26Z: released the stale claim 2026-10-04T03:20:54Z-020a8f on #742 and #650 (only the hosted slice merged in #743, no vendored PR, claimer silent for more than 48h)
• 2026-10-06 13:26Z: removed agent:claimed from 34 closed issues (#417, plus 33 closed by the 2026-10-05 13:39–18:16Z merge wave)
• 2026-10-06 13:26Z: posted drift comments on ledgers #319 (Gradle: 12 issues closed by #646 still listed as fail), #307 (#372), #316 (#709), #320 (#627) and #302 (#432)
• 2026-10-05 13:35Z: closed #473 as completed (PR #625 9df2afa5 said "Fixes #606 and #473", but only #606 auto-closed; include_group_member test on main)
• 2026-10-05 13:35Z: closed #566 as completed (PR #611 2465131e; site config layer read in pdm_global_site_packages_with)
• 2026-10-05 13:35Z: closed #603 as completed (PR #605 46466931; verify_mode_requires_every_store_copy_patched covers the Deno _1 case)
• 2026-10-05 13:35Z: posted a not-closing comment on #742 and #650 (PR #743 fixed only the hosted half; the vendored half is still open)
• 2026-10-05 13:30Z: removed agent:claimed from 49 closed issues (46 closed by the 11:13–13:20Z merge wave, plus #473, #566 and #603 above)
• 2026-10-05 13:35Z: posted drift comments on ledgers #306, #307, #308, #309, #310, #311, #312, #313, #314 and #316 (they cite issues closed today as fail)

Deferred / unsure

• #1665 (sbt 1.2.8 warm-cache hang): all 4 stalls fell inside 2026-10-22 05:53–09:47Z, and nothing has recurred since. There's no fix on main, so it stays open. Close it if it hasn't recurred by 2026-10-29.
• #549: open PR #1698 (Go patch delivery) may fix it; check once #1698 merges.
• #1089: criterion 3 is met (re-verified 2026-10-25), but criterion 2 isn't (435 sentence assertions are left), so it stays open.
• #1650: step 1 (diagnostics) merged in #1652; step 2 (bounded retry) waits on the next occurrence.
• #1588: fix PR #1590 merged 2026-10-17, and #1692 moved the compatibility workflows off Node 20. The issue has agent:needs-human, so the janitor leaves it; a human can close it.
• #1607 (yarn-berry rescan): #1693, #1695 and #1701 merged; it now has agent:needs-human. It's labeled pm:yarn, though other berry issues use pm:yarn-berry.
• #1424, #1425, #1472 (perf regressions from 10-13 bench readings) and #761, #836, #1246 (slow-scan issues): no bench reading since 2026-10-17, so whether #1684, #1695 or #1701 helped them can't be checked.
• #1052 asks for a port to depscan's composer-lock-members.ts, which isn't in this repo; it's tracked here on purpose because depscan has issues disabled.
• #780 and #594: arch-audit refactors with their hosted slices merged; the vendored slices are still open work.

Needs a human

• The bug-hunt fleet has been silent for about 7.5 days. The last commit on bughunt/ledger is 2026-10-18 01:27Z (pnpm). Every ledger now lists issues that were fixed since; see the drift comments. Please check the bug-hunt schedules.
• The benchmark routine has been silent since 2026-10-17 07:24Z (last bench/ledger commit). #575 hasn't changed since 2026-10-16, and the perf-regression issues can't be re-measured.
• Open agent:needs-human decisions: #267, #686, #691, #1065, #1099, #1109, #1130, #1200, #1248, #1352, #1512, #1588, #1607, #1660, #1670, #1720.
• 20 PRs are open, among them dependabot #1702 (zod 3 → 4 major bump), 15 agent fix PRs waiting on review, and CI PRs #1698, #1708 and #1716.
• The janitor/ledger branch requires verified signatures. This session's default git identity signs commits; overriding user.name/user.email breaks the signature.
• Discussion #301 ("Welcome to socket-patch Discussions!") is closed. The janitor keeps it as is.

---

Generated by Claude Code

[github-actions[bot]]

[agent] Janitor: bridge test. The janitor/ledger workflow posted this comment on the routine's behalf. Hourly runs log here from now on.

---

Generated by Claude Code