Skip to content

node-tools

Node CI image: node, npm, corepack (pnpm/yarn) for Svelte/frontend builds. Derives from ci-base.

Release v0.2.5, 2026-11-07. Built on ci-base. Source: phpboyscout/images/node-tools.

Pin it

image: registry.gitlab.com/phpboyscout/images/node-tools:v0.2.5

Pin the full version. Each release also moves its minor tag and latest, which change under you.

Variant Tags
default v0.2.5, v0.2

Later releases (v0.2.6) are tagged but have no image, because their publish was held, so this page describes v0.2.5.

About this image

The frontend track's CI image.

registry.gitlab.com/phpboyscout/images/node-tools:vX.Y.Z

Contains node and npm, on top of ci-base.

Serves svelte-build, svelte-lint, svelte-test and svelte-security.

playwright-tools is built FROM this image, so a release here reaches it through a Renovate bump.

Why it exists

A Svelte repository was pulling 2.7 GB to run npm ci — 920 MB of it a Rust toolchain and 270 MB a Go one, neither ever invoked.

size gate-visible findings
dev-tools 977 MB 66
node-tools 112 MB 7

This is the largest proportional saving of any track in the split: −89%.

The 7 remaining findings are Node's own bundled dependencies, and they are the same 7 that showed up as "Node.js" in dev-tools' breakdown — inherited, not introduced.

It stays non-root

Unlike go-tools and rust-tools, which need root because GitLab's helper checks out /builds as root and the Go module cache is written there.

Node has no equivalent requirement: svelte-build sets npm_config_cache to $CI_PROJECT_DIR/.npm, and tofu-tools (which replaced infra-tools) runs non-root writing into $CI_PROJECT_DIR for the whole Tofu track — so this is proven rather than assumed.

If an npm permission error ever appears, the fix is to look at what owns the checkout, not to reach for root.

No mise

Node comes from its official distribution, verified against the SHASUMS256.txt nodejs.org publishes beside it, pinned by an annotated ARG that Renovate tracks. Measured on tofu-tools, mise lost on every axis: a 23s against 9s cold build, two Renovate managers against one, GitHub API version-resolution against plain downloads, and no checksum verification at all.

The archive is .tar.xz; ci-base already provides xz and a tar that handles it, so nothing extra is installed. The sum is looked up by filename in SHASUMS256.txt rather than assumed to be a particular line — that file lists every artefact for the release.

No npm install -g npm. The bundled npm is the one tested against this Node, and upgrading it in the image would put a version nothing pins into every consumer's build.

The scan is split by who can fix it

Job Scope Gate
scan:os OS/apk packages — the base and anything we install hard
scan:tools Node's own bundled dependencies advisory

Consumer dependencies are deliberately not scanned here. They live in the consumer's lockfile, and svelte-security already scans them there with npm-audit, osv-scanner, retire.js and audit-signatures. Scanning them in the image would duplicate that — and worse, would gate the image on a consumer's dependency.

Design record

cicd spec 0074

Everything installed

Contents not yet published. This image's releases do not carry an SBOM yet. Until they do, the README above describes what it adds, and the Dockerfile is the full record.