A scan that really runs
Not a screenshot: a real scan in our production database, rechecked every day by the same scheduled job as the scans of our users. Its history grows while you read this page.
The file for a whole product
Its state, right now
Subject: euvex-demo-passerelle-thermique · version 2.4.1.
components
6
inventoried
vulnerabilities
54
known, via OSV and NVD
checks
18
kept
since the last one
2 hours
4 November 2026 at 18:20
What to look at
Three things a screenshot cannot show.
The history
In the printable file, the “Surveillance dans le temps” section (monitoring over time): one timestamped line per check. It has 18 entries today. Come back tomorrow, there will be one more.
The gaps, if any
If monitoring stops, the file names the gap instead of letting you believe nothing changed. It shows here just as it does for a user: we do not give ourselves a more flattering display.
The archive
Download it: each revision in it is a complete CycloneDX BOM, dated at its capture. Two downloads with no new check in between give the same file, byte for byte.
What this demo is not
euvex-demo-passerelle-thermique so that there is no ambiguity. The components and their vulnerabilities, however, are real: real npm packages and real advisories from OSV.Yours, in thirty seconds
npm, pnpm, yarn, or an existing CycloneDX or SPDX SBOM. A free account is enough, and the lockfile is not kept.