We’re building Omni Line around a simple belief:
Your software supply chain should be a place you can trust.
Our vision is to bring everything your team depends on to build and ship software into one system.
Java4Shell (CVE-2026-114938) exposes a blind spot: dependency scanners won't catch runtime vulnerabilities.
Learn how to inventory exposed JVMs, assess risk, and patch your fleet before attackers do.
https://t.co/vaa8tvrNqe
omni-audit v0.11.0 is out.
The new check command lets AI agents verify a package before adding it to a project.
It returns allow, block, or unknown, and suggests the correct name for clear typosquats.
Agents install dependencies on their own. Now they can ask first.
At Omni Line, we work on this problem every day: helping teams identify vulnerabilities and block malicious packages.
We welcome more voices making this conversation accessible to developers.
Congratulations on the new role, Erick!
Great to see @erickwendel_ joining @vltpkg and bringing more attention to package management and security.
His reach and experience in developer education can help more teams understand what enters their projects when they install a dependency.
E a nova aventura começou por aqui, meus amigos 🚀🚀
Que honra contribuir com a galera que está viva no open source, atuando na parte mais sensível da cadeia produtiva: o gerenciamento de pacotes.
Com a @vltpkg você publica pacotes de forma simplificada, com foco em segurança e performance.
Bora pra cimaaaaaaa 🚀 🚀🚀🚀🚀
A package registry should do more than store and serve dependencies.
It should help you understand what you're running, detect vulnerabilities, enforce security policies, and keep CI pipelines moving.
Read the full breakdown:
https://t.co/zBeLErNwph
Since Omni Line 1.0, we've shipped 10 releases in just a few days.
Not just new features. We fixed real problems we found running a registry in production.
Two areas got major improvements: vulnerability visibility and CI performance.
Here's what changed. 🧵
Now, CI performance.
We found that even cache hits were fetching and processing upstream metadata before serving cached packages
After fixing that
npm install: 15.6 min → 14–27 sec
composer install: 30+ min → 25–37 sec
Same warm-cache scenario. Dramatically faster installs.
omni-audit, our open-source CLI, is now part of the @xerj_org Corpus Hub.
It audits projects for dependency confusion and other supply-chain risks across multiple package registries.
The project is available in the hub under the MIT license.
The Omni Line blog is now available in Portuguese, Spanish and German.
Every published or scheduled post is translated automatically, with code blocks, links and headings kept intact.
Which language should we add next?
Can you cut install/publish blast radius in 1-2 hours? We recommend a Phase A pilot: route one ecosystem's CI to an internal proxy registry, issue short-lived tokens that include CI_RUN_ID, and verify correlation via your registry audit stream
https://t.co/PRbg5WAtUk
o omni-audit ganhou bastante coisa entre ontem e hoje.
pra quem não conhece: é uma cli em go, open source, que olha o seu projeto atrás de risco nas dependências. nome interno que ainda tá livre no registry público e que qualquer um pode registrar, nome parecido com pacote famoso, e lockfile puxando direto da internet em vez do proxy da empresa.
o que entrou agora:
checagem de pacote malicioso. cada dependência e cada versão travada no lockfile é comparada com os 239 mil alertas de malware da openssf. tudo offline.
auditoria de configuração. um --extra-index-url no pip já basta pra um pacote público com versão 99.0 ganhar do seu pacote interno. foi assim que o torchtriton chegou em quem usava o pytorch nightly em 2022. ele também pega token em texto puro no .npmrc e registry rodando em http.
e uma github action, que baixa o binário, confere o checksum e roda no ci.
a base de malware vem do mal-check, o irmão dele. o mal-check faz só isso: lê os lockfiles de npm, pypi, rubygems, nuget, crates, go, composer e até as extensões do vs code, e diz se algum pacote foi publicado como malware. é um binário só, sem rede, nada sai da máquina.
ele pega tanto pacote que já nasceu malware quanto pacote legítimo que teve versão sequestrada, tipo chalk e axios.
e se aparecer algo, atualizar não resolve. o código roda na instalação, então é hora de trocar os tokens que aquela máquina tinha.
30 CVEs and eight compromised CA keys in eight days — triage by how the fix ships. Prioritize internet-facing RCEs, then rebuild embedded artifacts, then trust stores. Assign owners, a definition of done, and a proof for each advisory.
https://t.co/JeyzC06YkU
We classify CI jobs by capability and lifespan: prefer short‑lived OIDC for ephemeral installs, narrowly scoped PATs for publishes, centralize traffic behind one registry hostname, and publish a rotation + rollback runbook.
https://t.co/Hsi1OhTLaU
We recommend: assume compromise and route installs through a canonical internal registry/proxy for telemetry and containment. Pin and mirror audited SHAs, enforce lockfile‑first installs, and rotate tokens for runners that ran suspicious packages.
https://t.co/S37DHRIhY3