Skip to content

fix: remove sensitive query logs and patch dependencies - #60

Merged
jmgasper merged 1 commit into
devfrom
fix/security-findings-2026-11
Nov 2, 2026
Merged

jmgasper merged 1 commit into
devfrom
fix/security-findings-2026-11

Conversation

@jmgasper

@jmgasper jmgasper commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Remove clear-text Salesforce query logging and patch the application/container dependency graph. Queries now emit a fixed diagnostic message, with a regression test preventing configured fields and billing-account IDs from entering logs. Update Node 26 / Alpine 3.24, Prisma 7.10.1 and the reviewed immutable core-library revision while retaining the existing external Prisma-client commit pins.

Replace obsolete ESLint/Ajv patches with patched compatible Ajv releases and add a tested minimatch adapter. Update stale metadata test expectations to match the already-retired event publisher; production metadata event behavior is unchanged.

Validation:

  • Full audit: zero critical/high/medium, one low; all 46 original target Dependabot findings patched or removed.
  • Final production image: zero critical/high/medium Trivy findings.
  • Docker lint/build, 529 unit tests and 2 matcher tests pass (3 existing conditional unit tests skipped). The Salesforce logging regression is included.
  • All repository migrations apply to fresh local PostgreSQL. Final-image health and authorized project reads return 200; missing, malformed and expired JWTs return 401. Node 26.12.1 / UID 10001.

Targets the active dev branch. GitHub code scanning will validate the logging remediation on this PR. No deployment or production data changes.

@jmgasper
jmgasper merged commit 635b71e into dev Nov 2, 2026
5 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