pnpm
Runtime · Build tool · standard · v11.19.0
Node base image with pnpm preinstalled via corepack, used as the build stage for pnpm projects. Lines 10/11.
Security report (Trivy)
Security report (Trivy) · pnpm 11.19.0
Published versions
1 tagEach tag is a multi-arch index (amd64 + arm64) pinned by digest. Tagged by version, never :latest.
| Version | Size | Published | Digest |
|---|---|---|---|
| 11.19.0latest | 60.6 MB | 2026-08-02 | sha256:5e71ddcd82f2… |
Use it as a base image
Reference it in the FROM line of your Dockerfile. Nonroot, read-only root filesystem, built for amd64 and arm64.
FROM ghcr.io/quenchworks/images/pnpm:11.19.0Or pull it directly
docker pull ghcr.io/quenchworks/images/pnpm:11.19.0- Version line
- 11.19.0
- Latest line
- 11.19.0
- Architectures
- amd64, arm64
- Runs as
- nonroot (uid 1001)
- Root filesystem
- read-only
- License
- MIT
Verify the supply chain
This image is cosign-signed and carries an SPDX SBOM and a SLSA build-provenance attestation on the same digest. Check all three before you build on it:
# 1. signature — built and signed by QuenchWorks CI
cosign verify ghcr.io/quenchworks/images/pnpm:11.19.0 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 2. SLSA build provenance — which workflow built it, from what
cosign verify-attestation --type https://slsa.dev/provenance/v1 ghcr.io/quenchworks/images/pnpm:11.19.0 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 3. SPDX SBOM — the package inventory
cosign verify-attestation --type https://spdx.dev/Document/v2.3 ghcr.io/quenchworks/images/pnpm:11.19.0 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comSee the SBOM & provenance guide for reading the SBOM and using these checks in CI.
Best-practice Dockerfile for 11.19.0
pnpm leads: enabled here through corepack on the pnpm base, it resolves and locks the dependency set, builds, then a clean node base receives only the production node_modules and the built output.
# Build stage: pnpm resolves, locks, and builds (dev deps included here).FROM ghcr.io/quenchworks/images/pnpm:11.19.0 AS buildUSER rootWORKDIR /appENV PNPM_HOME=/tmp/pnpm
COPY package.json pnpm-lock.yaml ./RUN ["pnpm", "install", "--frozen-lockfile"]COPY . .RUN ["pnpm", "run", "build"]# Re-resolve to production-only for the runtime stage.RUN ["pnpm", "install", "--prod", "--frozen-lockfile"]
# Runtime stage: prod node_modules + built dist on a slim node base, nonroot.FROM ghcr.io/quenchworks/images/node:26.5.1 AS runtimeWORKDIR /appENV NODE_ENV=productionCOPY --from=build /app/node_modules ./node_modulesCOPY --from=build /app/dist ./distCOPY --from=build /app/package.json ./package.jsonUSER 1001EXPOSE 3000CMD ["node", "dist/server.js"]This Dockerfile is pinned to the 11.19.0 line. For the line-by-line walkthrough and ecosystem variants (npm/Yarn, pip/uv/Poetry, Maven/Gradle), see the Build a Node appguide.
Upstream project: https://pnpm.io