Skip to content

NPM supply-chain audit and vulnerability fixes#12

Open
agit8or1 wants to merge 1 commit into
mainfrom
chore/npm-supply-chain-audit-2026-06
Open

NPM supply-chain audit and vulnerability fixes#12
agit8or1 wants to merge 1 commit into
mainfrom
chore/npm-supply-chain-audit-2026-06

Conversation

@agit8or1

@agit8or1 agit8or1 commented Jun 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • Audited npm/pnpm dependencies for supply-chain compromise indicators
  • Applied safe lockfile-only dependency updates
  • Added audit before/after reports
  • Pushed branch chore/npm-supply-chain-audit-2026-06

Results

No obvious Shai-Hulud-style compromise indicators were found.

Notes

  • No install scripts were executed
  • No node_modules install was performed
  • No production paths were touched
  • No token/env files were staged

Follow-up

See npm-supply-chain-audit-report.md and related SECURITY-NPM-AUDIT files for remaining advisories and manual migration notes.

Defensive sweep against the active Shai-Hulud / Mini Shai-Hulud npm
supply-chain incident. All work in --package-lock-only --ignore-scripts
mode; no installs, no script execution.

agent/:
- Had package.json but NO package-lock.json — installs would pull
  "latest matching" versions without integrity verification, exactly
  the attack window the current campaign exploits. Generated a clean
  lockfile via `npm install --package-lock-only --ignore-scripts`.
  Lockfile audits clean (0 advisories).

backend/:
- 3 moderate (qs / body-parser / express via qs) → 0.

frontend/:
- 2 moderate (react-router / react-router-dom) → 0.

No supply-chain indicators found:
- No @tanstack/* / @antv/* / @redhat-cloud-services/* / @mistralai/* /
  @bitwarden/cli / plain-crypto-js declared anywhere
- No axios@1.14.1 / axios@0.30.4 (resolved 1.16.1 in backend+frontend)
- All resolutions integrity-pinned to registry.npmjs.org
- No git+ / github: / file: / http: resolutions
- No .npmrc / .yarnrc anywhere

Follow-up: switch CI installs to `npm ci` (lockfile-strict) so the
integrity gap can't reopen.

See per-package SECURITY-NPM-AUDIT.md and npm-supply-chain-audit-report.md
(global, covers Depl0y + St0r + rem0te) for details.
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