Overview
A NIM container is an OCI image published to NVIDIA’s container registry (nvcr.io/nim/...). The container includes a model_manifest.yaml that describes deployment profiles and references model weight files stored on NGC using ngc:// URIs.
Scanning the container itself is not the same as scanning the full model:
- Container scan — Flattens the image, scans files inside the container filesystem, parses
model_manifest.yaml, and emits an advisory with manifest evidence. External artifact URIs are collected intosummary.referenced_modelsin v3 output. - Follow-up scan — Downloads referenced NGC artifacts out-of-band and scans the model files locally using Supply Chain CLI.
Model Manifest
During a NIM container scan, the scanner looks formodel_manifest.yaml at:
opt/nim/etc/default/model_manifest.yaml(current layout)etc/nim/config/model_manifest.yaml(legacy layout)
- model — The default model identifier (for example,
nvidia/test-model). - release — The model version.
- profiles — Deployment profiles, each with a workspace section listing files and their
ngc://URIs.
Model Reference Advisory
NIM container scans emit advisoryCONTAINER_0001_202606. This advisory indicates that the scanned input is a container with NIM runtime metadata. Review the manifest evidence and referenced model URIs before deploying the container.
When the scanner parses the manifest, external artifact URIs from profile workspace files are also collected into summary.referenced_models in v3 JSON output. The list is deduplicated across all profiles.
Example v3 summary excerpt:
For Model-Free Containers, the advisory is emitted, but
referenced_models is empty as the manifest isn’t present in the container image.
