Skip to content

chore: supply-chain hardening - #66

Open
erik1o6 wants to merge 2 commits into
masterfrom
security/hardening
Open

chore: supply-chain hardening#66
erik1o6 wants to merge 2 commits into
masterfrom
security/hardening

Conversation

@erik1o6

@erik1o6 erik1o6 commented May 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Pin all direct dependency and devDependency specs in package.json to exact versions and add engines constraints for Node/pnpm.
  • Add .nvmrc, .npmrc, and pnpm-workspace.yaml hardening defaults (engine-strict, save-exact, audit-level=high, fund=false, minimumReleaseAge).
  • Update Docker install step to pnpm install --frozen-lockfile for immutable image builds.
  • Make Husky shell hooks (pre-commit, pre-push) POSIX-safe so validation runs reliably.

Test plan

  • nvm use 22 && pnpm install --lockfile-only
  • nvm use 22 && pnpm install --frozen-lockfile
  • nvm use 22 && pnpm run build
  • rg -n '\":\\s*\"[~^]' package.json returns no matches

erik1o6 added 2 commits May 11, 2026 21:31
Pin direct dependency specs and enforce stricter pnpm/Node install policy so local and container builds use immutable lockfile installs with a release-age gate.
Replace bash-specific nvm parsing in the pre-push hook with a POSIX-safe setup so hook execution is reliable in standard sh environments.
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