Skip to content

fix: resign pnpm/yarn JS entrypoints on firewall trust - #29

Merged
coreybutler merged 1 commit into
mainfrom
fix/sign-pnpm-mjs
Nov 3, 2026
Merged

coreybutler merged 1 commit into
mainfrom
fix/sign-pnpm-mjs

Conversation

@coreybutler

Copy link
Copy Markdown
Contributor

What

Resign nested pnpm/yarn JS/CJS/MJS entrypoints (and standalone PNPM_HOME *.mjs) when nvm firewall trust module runs — not only top-level .cmd/.bat.

Why

Proxy prefers pnpm.mjs over the cmd wrapper. Trust that only signed pnpm.cmd left the real entrypoint unsigned → NVM4306 on next launch.

Testing

  • Compiles against common PackageManagerCliRelPathsFor.
  • Manual: trust pnpm after install; confirm pnpm --version succeeds.

Risk

Low. Only expands which existing on-disk paths get SignScript after an explicit trust action.

nvm firewall trust module previously re-signed only .cmd/.bat launchers.
Proxy launches pnpm.mjs (and yarn.js/.cjs/.mjs), so trust left the real
entrypoint unsigned and the next run hit NVM4306.

Resign nested package-manager JS/CJS/MJS paths from
PackageManagerCliRelPathsFor, plus standalone PNPM_HOME *.mjs/*.cjs/*.js.

Signed-off-by: Corey Butler <corey@author.io>
@coreybutler
coreybutler merged commit ce2fa38 into main Nov 3, 2026
8 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant