Issues · SocketDev/socket-patch

With several Poetry envs for one project (`poetry env use` on two Python minors), agent mode patches the alphabetically first env instead of the one Poetry activated, and VEX attests not_affected

SocketDev/socket-patch#526 · opened

on Oct 2, 2026

1

uv projects whose env is set by UV_PROJECT_ENVIRONMENT are never probed: agent scan patches the PATH interpreter and uv tool envs instead, the real env stays vulnerable, and vex attests not_affected

SocketDev/socket-patch#525 · opened

on Oct 2, 2026

uv rollback, remove and vendor --revert leave an empty `[tool.uv.sources]` header behind when the project's sources are written as `[tool.uv.sources.<name>]` sub-tables

SocketDev/socket-patch#524 · opened

on Oct 2, 2026

Lockfile-only requirements.txt discovery skips exact pins written with spaces (`six == 1.15.0`, `six (==1.15.0)`), so a fresh checkout reports "No patches available" and pip installs the unpatched release

SocketDev/socket-patch#523 · opened

on Oct 2, 2026

vlt hosted rollback and remove rewrite slot [3] to a synthesized `/<name>/-/<leaf>-<ver>.tgz` URL instead of the registry's dist.tarball, so the next cold `vlt ci` 404s

SocketDev/socket-patch#521 · opened

on Oct 2, 2026

1

In a yarn classic Plug'n'Play project, `vex` attests a hosted patch as not_affected while the copy .pnp.js loads is still unpatched

SocketDev/socket-patch#519 · opened

on Oct 2, 2026

2

npm crawler never looks in Rush's common/temp store: hosted `vex` attests a transitive dep not_affected while its installed copy is unpatched, and agent apply reports it package_not_installed

SocketDev/socket-patch#518 · opened

on Oct 2, 2026

3

Agent-mode npm `vex` hashes only the first installed copy of a package, so it attests not_affected while another nested copy of the same name@version is unpatched

SocketDev/socket-patch#516 · opened

on Oct 2, 2026

4

Composer vendored repair (and re-vendor) rebuilds a deleted uuid dir without its socket-patch.vendor.json marker, leaving git showing the marker as deleted

SocketDev/socket-patch#515 · opened

on Oct 1, 2026

1

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

SocketDev/socket-patch#514 · opened

on Oct 1, 2026

1

Vendored Maven reactor reports applied and VEX attests not_affected when a ${property} version is left unresolved, so the build keeps Central's unpatched jar (also triggered by Maven 4 <parent/> inference)

SocketDev/socket-patch#513 · opened

on Oct 1, 2026

1

Vendored Gradle silently downgrades a version-range dependency to an older unpatched release (1.10.0 → 1.9), because the vendored repository has no maven-metadata.xml; vendor --check and VEX still report it patched

SocketDev/socket-patch#511 · opened

on Oct 1, 2026

1

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

SocketDev/socket-patch#509 · opened

on Oct 1, 2026

1

Gem manifest resolution lets the `BUNDLE_GEMFILE` env var override `.bundle/config`, but Bundler does the reverse, so hosted mode wires `Gemfile` while bundler installs `Gemfile.next` unpatched and VEX attests it

SocketDev/socket-patch#507 · opened

on Oct 1, 2026

1

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

SocketDev/socket-patch#506 · opened

on Oct 1, 2026

1

Vendored scan in a Hatch workspace member writes {root:uri} that the workspace root env never expands, so every hatch run at the root fails to install

SocketDev/socket-patch#505 · opened

on Oct 1, 2026

1

Agent-mode scan in a Pipenv project without a Pipenv venv patches the system Python's site-packages in place instead of the project's venv/ (regression from #388)

SocketDev/socket-patch#504 · opened

on Oct 1, 2026

1

Agent and hosted mode ignore the interpreter PDM records in .pdm-python (venv.in_project = false, pdm use <venv>), so the real env is skipped or a stray .venv / the PATH python is patched, and VEX attests an unpatched install

SocketDev/socket-patch#502 · opened

on Oct 1, 2026

2

With the same release in user site-packages and a system site-packages dir, agent mode patches the shadowed system copy, leaves the copy Python imports unpatched, and VEX attests it (worse since #452: now hits apt-installed packages)

SocketDev/socket-patch#501 · opened

on Oct 1, 2026

1

`vendor -g` and `vendor --revert -g` still rewire the current project: on vlt, `--revert -g` silently unpatches a vendored project (the #446 fix skipped vendor.rs)

SocketDev/socket-patch#498 · opened

on Oct 1, 2026

3

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)

SocketDev/socket-patch#497 · opened

on Oct 1, 2026

2

Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched

SocketDev/socket-patch#495 · opened

on Oct 1, 2026

3

Agent mode ignores yarn classic's `--modules-folder`: packages installed there are reported "not installed" and `scan --mode agent` exits 0 leaving them unpatched

SocketDev/socket-patch#493 · opened

on Oct 1, 2026

5

Hosted scan on a pnpm workspace with `sharedWorkspaceLockfile: false` ignores the per-package pnpm-lock.yaml files and reports success while redirecting nothing

SocketDev/socket-patch#492 · opened

on Oct 1, 2026

2

npm hosted and vendored modes refuse a registry-installed package when its dependent's git spec is replaced by an `overrides` entry (regression from #345)

SocketDev/socket-patch#490 · opened

on Oct 1, 2026

2