wrote about everything that changed in OmniLine since 1.0.
that's 10 releases in 5 days.
i compared the dashboard with a real project's lockfile.
the dashboard said 17 open vulnerabilities.
none of them were on a version the project uses today.
and the one that mattered didn't show up, because github's advisory was wrong.
now the count follows what each project and environment actually runs.
an environment that stops reporting no longer shows up as clean.
composer scans read two vulnerability databases instead of one.
and a cached ci install went from over 15 minutes to under 30 seconds.
the post has the numbers, the mistakes and what's still not covered.
https://omniline.app/blog/omni-line-since-1-0-vulnerability-counts-faster-ci-installs

Omni LineOmni Line since 1.0: vulnerability counts that follow what you run, and faster CI installsCounts per project and environment, no false clean, two advisory databases, faster CI installs. What changed in Omni Line 1.0.0–1.0.9, and why.
commit 05e2485