‹tool› installs brand-new package versions with no waiting period (‹path›)
What this means
Malicious package releases are usually caught and removed within hours or days. With no waiting period set in ‹path›, ‹tool› installs a version published minutes ago, which is the window attackers rely on. A short delay lets the registry and scanners catch a bad release before it reaches this machine.
How to fix it
npm: Run npm config set min-release-age 7 for a 7-day waiting period (needs npm 11.10 or newer; check with npm --version). For an urgent security patch, override once: npm install <package> --min-release-age=0.
bun: Add these two lines to ~/.bunfig.toml for a 7-day waiting period (the value is in seconds): [install] and minimumReleaseAge = 604800. Exempt a package you trust with minimumReleaseAgeExcludes.
uv: Add the line exclude-newer = "1 week" to ~/.config/uv/uv.toml (on Windows: %APPDATA%\uv\uv.toml). For one urgent install, pass --exclude-newer with today's date.
Check it yourself
Run a scan and look for BLWK-DEV-011 in the results:
bulwark scanInstalled the standalone CLI package instead of the app? The command is bulwarkctl.
How Bulwark decides
Bulwark reads dev_tool_config and reports this check when:
kind in ["npm_user", "bun_user", "uv_user"] and no_release_cooldown == trueIf a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.
References
Related checks
- Git skips TLS certificate checks (‹path›) ·
BLWK-DEV-001 - Git trusts repositories owned by anyone (‹path›) ·
BLWK-DEV-002 - Git allows the ext:: transport, which runs commands from a URL (‹path›) ·
BLWK-DEV-003 - SSH doesn't check server identities (‹path›) ·
BLWK-DEV-004 - SSH forwards your agent to every server (‹path›) ·
BLWK-DEV-005 - npm/yarn installs packages without checking TLS certificates (‹path›) ·
BLWK-DEV-006