AI supply chain: what enters before the model runs
A model is one part of what a system runs. Datasets, weights, packages and plugins arrive from elsewhere, and any of them can change the behaviour of the whole.
We start with the inventory: which components are used, where they came from, and what their licences allow. Most incidents in this layer begin with a component that nobody remembers adding.
Then we check behaviour, not only paperwork. A package can pass every scanner and still execute at the wrong moment; a dataset can be clean by metadata and skewed by selection. Both are tested, and both are written into the report.
The output is a component map with findings and a list of what we did not verify. We do not certify the supply chain. We show what was checked, and how.