Skip to content
LowSupply chainBLWK-DEV-011

‹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:

sh
bulwark scan

Installed 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:

text
kind in ["npm_user", "bun_user", "uv_user"] and no_release_cooldown == true

If a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.

References ​

Released under the Apache License 2.0.