🚀 Just shipped a new `vlt skills` cmd as part of v1.5.0 of the vlt CLI so that we can properly manage these skills that are already being shipped in packages.
.@vltpkg 1.5.0 links agent skills from your dependencies to coding agents, with versions pinned by your lockfile.
The default skills filter uses Socket data to exclude packages flagged as malware before their instructions reach your agents.
https://t.co/bNunYgaJwn
🚀 Just shipped a new `vlt skills` cmd as part of v1.5.0 of the vlt CLI so that we can properly manage these skills that are already being shipped in packages.
I thought I'd share some of my thoughts/feelings about the recent Deno acquisition... tl;dr competition is a very good thing & we're all better off because people take risks to innovate & disrupt the status quo. [link below]
on the ⚡️@vltpkg ⚡️registry we serve metadata that is 70% smaller which is one reason (out of many!) that we're able to do clean installs in 20-70% less time when you point to our registry vs npmjs․org. i wrote about how we did it: https://t.co/8KENtzX4qN
Your private JavaScript registry can now publish to the public.
Public packages are now GA. Publish and install the packages you want to share with the ecosystem. Read the full announcement here ↓ https://t.co/A0ddNeGrfv
🚀 Thrilled to announce @vltpkg as a #Silver#Sponsor of #NodeConfEU 2026!
Thank you! 💛
Your partnership is helping us create something truly special in the #Node.js #community!
🎟️ https://t.co/rDKt7ktI66
This can't be overstated. Funny enough, dual support outpaces esm-only (expected, as maintainers want the broadest interop). We're almost a decade in & esm-only pkgs are only growing at ~2% /yr; at that pace, it'd take another decade to hit ~50%.
refs. https://t.co/y2Ml96Iru2
vlt 1.0.5 is here 🚀
Faster installs when package.json declares duplicated depedencies: up to 40% smaller.
Safer installation and package publishing by default: tar decompression caps & path-traversal hardening enforced. https://t.co/uMbIAfO30e