← Founder Notes
Archive

The original npm team shipped vlt 1.0, a drop-in npm replacement that blocks script execution on…

Yethikrishna ROriginal on Threads

the original npm team shipped vlt 1.0, a drop-in npm replacement that blocks script execution on install by default. the supply chain fix everyone asked for came from the people who built the original problem.

your package manager just became a security product.

Context

The vlt blog post of 4 August 2026 announces vlt 1.0 and general availability of hosted registries, and describes the client as a drop-in replacement for npm. It says vlt install can download without running scripts through phased installation, and that vlt build runs scripts selectively and blocks known malware by default. InfoQ, dated 7 September 2026 and seen as a snippet, says vlt was built by npm's original creators.

How it compares

The release is dated 4 August, not September. The original npm team phrase is supported only at secondary snippet level. The post says build blocks known malware by default and install downloads without scripts; it does not state that script blocking is the default for every install, so the note's wording is a simplification. Coming from the people who built the original problem is the author's opinion.

Related work

Watch next

  • vlt release notes after 1.0 and a first-party statement of the default script policy.

Sources

  1. vlt 1.0 (vlt blog, 4 Aug 2026)vlt.io

Provenance

The note above is reproduced unedited from the original post, first published on Threads on 18 September 2026 at 06:01 IST. Sources are the papers and datasets the note draws on.

View the original post
Embed this note
<iframe src="https://founder.myndlabs.tech/notes/embed/the-original-npm-team-shipped-vlt-1-0-DdaJzViiHBg" width="480" height="420" style="border:0;max-width:100%" loading="lazy" title="The original npm team shipped vlt 1.0, a drop-in npm replacement that blocks script execution on…"></iframe>

More notes