vlt /vōlt/

@vlt.io

The package platform built for JavaScript.

You can't improve what you don't measure. And measure, we do. 😉 A clean install runs up to 38% faster than npm, no change to your tooling required.

Bild

Excited to share vlt 1.0 along with our hosted registries & ecosystem mirrors now GA! A drop-in npm replacement, built so nothing runs on your machine just because you typed install. → faster delivery → malware blocking at the registry layer → graph-native querying

🐚→🌳 unbash v4.0.6 is out unbash will change the game: more modern and complete syntax support + great performance Cuts whole dependency trees and expensive wasm loaders 🪓 Today, fixed a bunch of edge cases and improved docs + comparisons. Stay tuned.. → github.com/webpro-nl/un...

Last month Drizzle ORM couldn't publish a new release to npm for weeks. Not a bug in their code. Their metadata file crossed npm's 100 MB limit, & the only fix was asking npm support to delete old versions by hand. 🧵

reporting emails as spam is doing a civic duty for everyone else because the more spam complaints a sender receives, the bigger impact on their deliverability do your civic duty today and every slop spam email you get, report it as spam

Your AI assistant just suggested an npm package. It looks real, it's well-named, it solves your exact problem. It also never existed until an attacker registered the name & filled it with malware. That's slopsquatting. 🧵

A familiar story: the build crashes, so you rm -rf node_modules && rm package-lock.json, then reinstall to get your dev env back. But once the lockfile's gone, your ^ ranges take over. npm install can grab the newest in-range version of everything: poison included when there's a supply chain attack

Ship JavaScript? Hang onto your lockfile | vlt /vōlt/

Pinning dependencies in package.json won't save you in a supply-chain attack — a committed lockfile does. Here's why, and how to install so it holds.

vlt.io

npm install runs arbitrary code by default. Lifecycle scripts — preinstall, postinstall — execute on your machine before you've imported a thing. We think that default is backwards. In vlt/cli they're restricted unless you opt in. Hardening shouldn't be a setting you remember to flip.

When agent skills and prompt techniques proliferate like trend cycles in product engineering, what happens to production? 🤔