Skip to content

[pull] latest from npm:latest#171

Merged
pull[bot] merged 3 commits into
DavidLacombe46:latestfrom
npm:latest
Jun 2, 2026
Merged

[pull] latest from npm:latest#171
pull[bot] merged 3 commits into
DavidLacombe46:latestfrom
npm:latest

Conversation

@pull

@pull pull Bot commented Jun 2, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

rootvector2 and others added 3 commits June 2, 2026 11:30
run() in libnpmexec wraps the executable name in double quotes before it
becomes the npx script string, but double quotes still expand $(),
backticks, $var and a closing quote, so a package whose bin key holds
shell metacharacters breaks out once the name reaches sh -c. The bin
name comes straight from a published package.json. Switch the
non-Windows branch to single-quote escaping so the name is taken
literally.
`npm pack` writes the tarball to a name built from `manifest.name` with
a non-global `.replace(/\//, '-')`, which only strips the single scope
slash. When packing a remote tarball, git, or directory spec the name
comes from a package.json that the registry never validated, so a name
like `x/../../../escaped` keeps its `../` segments and
`path.resolve(packDestination, filename)` lands the tarball outside the
destination. Make the separator replacement global so the filename is
always one path component.
BREAKING CHANGE:  allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.
@pull pull Bot locked and limited conversation to collaborators Jun 2, 2026
@pull pull Bot added the ⤵️ pull label Jun 2, 2026
@pull pull Bot merged commit caa3295 into DavidLacombe46:latest Jun 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants