mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 15:42:24 +00:00
build(docker): mirror the hono and valibot pins into /opt/prisma-cli
The image carries two installs. pnpm builds the app tree from pnpm-workspace.yaml; npm builds /opt/prisma-cli and reads only its own overrides field. The scan reported @hono/node-server@1.19.11 (GHSA-frvp-7c67-39w9, CVE-2026-39406) and valibot@1.2.0 (CVE-2026-59952) under that path while both packages were pinned and clean in the app tree. Same shape as the deepmerge-ts finding, same cause. Rebuilt this exact install both ways to confirm rather than assume. Without the two fields npm resolves @hono/node-server 1.19.11 and valibot 1.2.0, which are the two versions the scan named. With them it resolves 1.19.17 and 1.4.2, and prisma --version still reports 7.8.0. Both arrive through prisma -> @prisma/dev. The lockstep guard could not have caught this. Its workspace matcher started a package name at [^"@], so every scoped key was invisible to it: @hono/node-server was in the workspace file and absent from the Dockerfile, the shared set never contained it, and the guard stayed green. Scoped keys parse now, a test pins the reduction itself so the blind spot cannot return quietly, and a second test asserts that the three packages the image scan has actually flagged under /opt/prisma-cli keep their npm-side mirror. Both fail when the pin is removed or moved out of step.
This commit is contained in:
1 parent
f62cd59789
commit
c9f8aee476
2 files changed
+65
-4
No files matched your search
+10
@@ -191,11 +191,21 @@ COPY --from=builder /app/src/generated ./src/generated
|
||||
# still reports 7.8.0. Keep the range in step with the entry in
|
||||
# `pnpm-workspace.yaml` — they are one decision applied to two package
|
||||
# managers, and a fix that lands in only one of them is the defect above.
|
||||
#
|
||||
# The same class recurred on 2026-09-02: the image scan reported
|
||||
# `@hono/node-server@1.19.11` (GHSA-frvp-7c67-39w9, CVE-2026-39406) and
|
||||
# `valibot@1.2.0` (CVE-2026-59952) under this path, both reached through
|
||||
# `prisma -> @prisma/dev`, while the app tree carried 1.19.17 and a pin the
|
||||
# npm install never reads. Rebuilding this install both ways confirms it:
|
||||
# without the two fields below npm resolves 1.19.11 and 1.2.0, with them it
|
||||
# resolves 1.19.17 and 1.4.2, and `prisma --version` still reports 7.8.0.
|
||||
RUN mkdir -p /opt/prisma-cli && \
|
||||
cd /opt/prisma-cli && \
|
||||
npm init -y && \
|
||||
npm pkg set 'overrides.deepmerge-ts=^8.0.0' && \
|
||||
npm pkg set 'overrides.mysql2=^3.22.0' && \
|
||||
npm pkg set 'overrides.@hono/node-server=^1.19.15' && \
|
||||
npm pkg set 'overrides.valibot=^1.4.2' && \
|
||||
npm install --omit=dev prisma@7.8.0 @prisma/engines@7.8.0 tsx@4.23.1 dotenv@17.4.2 && \
|
||||
ln -sfn /opt/prisma-cli/node_modules/.bin/tsx /usr/local/bin/healthlog-tsx && \
|
||||
ln -sfn /opt/prisma-cli/node_modules/dotenv /app/node_modules/dotenv && \
|
||||
|
||||
Reference in new issue
Block a user