Skip to content

Supported Artifacts

Review the artifacts that BIMP currently supports during scanning

BIMP discovers concrete OCI image references in supported files on each scanned repository branch. Use this page to check whether a file and its image-reference format can appear in BIMP inventory, policy evaluation, and remediation.

Is there something missing on this page? Let us know at feedback.bimp.ai.

Recognized files can be at the repository root or in a subdirectory.

Artifact File or variation Discovery behavior
Dockerfile Dockerfile Discovers images in FROM instructions.
Dockerfile Dockerfile.* or *.Dockerfile Uses the same FROM rules.
Dockerfile Multi-stage build Finds every external FROM image.
Dockerfile Stage alias or scratch Skips the internal reference.
Dockerfile ARG in a FROM image Resolves defaults from the file.
Dockerfile Image made from several ARGs Resolves declared defaults.
Dockerfile Line continuation Reads the complete FROM instruction.
Dockerfile FROM --platform=... Records a concrete target platform.
Docker Compose compose.yaml or compose.yml Reads service images.
Docker Compose docker-compose.yaml or .yml Reads service images.
Docker Compose docker-compose.<name>.yaml or .yml Reads images.
Docker Compose Short-form build Follows the context’s Dockerfile.
Docker Compose Build context and Dockerfile Follows that Dockerfile.
Docker Compose build.dockerfile_inline Reads its FROM instructions.
Docker Compose Service platform Records a concrete target platform.
Docker Compose Variable in image Reports the reference as unresolved.
Dev Container .devcontainer/devcontainer.json Reads top-level image.
Dev Container Root .devcontainer.json Reads the top-level image.
Dev Container JSON comments and trailing commas Supported.
Dev Container String-form build Follows the referenced Dockerfile.
Dev Container Build context and Dockerfile Follows that Dockerfile.
Helm values values.yaml or values.yml Must be beside Chart.yaml.
Helm values values-<name>.yaml or .yml Must be beside Chart.yaml.
Helm values values.<name>.yaml or .yml Must be beside Chart.yaml.
Helm values Scalar image Reads the complete image reference.
Helm values Map-style image Requires a concrete repository.
Helm values registry, tag, and digest fields Optional map fields.
Helm values Nested maps, lists, or repeated images Supported.
Helm values Go-template expression Not resolved as an image.

Concrete image references can include a registry, repository, tag, and digest. For Dockerfile ARG values, a value supplied only as an external build argument is not available during a repository scan. For Compose, BIMP retains an image that uses environment-variable interpolation as an unresolved reference rather than guessing its runtime value.

BIMP does not render Helm charts or download chart dependencies. It discovers only concrete image values in chart-anchored values files tracked on the selected branch. More generally, an image generated only during a build or deployment is outside the repository scan.

BIMP does not currently discover image references from the following artifact types. References stored only in these files do not appear in BIMP inventory, policy evaluation, or remediation.

Artifact type Examples
Buildpack configuration Cloud Native Buildpacks and project.toml
Buildpack configuration Builder and platform-specific settings
CI/CD workflows GitHub Actions and GitLab CI
CI/CD workflows Jenkinsfiles, CircleCI, Buildkite, Azure Pipelines
Kubernetes manifests Pods, Deployments, StatefulSets, and DaemonSets
Kubernetes manifests Jobs and CronJobs
Helm templates Files under templates/ and rendered manifests
Helm dependencies Values supplied only by a dependent chart
Kustomize Image overrides, patches, and overlays
Infrastructure as code Terraform, OpenTofu, Pulumi, and CloudFormation
Infrastructure as code AWS CDK and Azure Bicep
Other container builds Bazel container rules, Earthly, Dagger, and Nix
Other container builds Buildah scripts
Development and deployment Skaffold, Tilt, DevSpace, and Garden
Other orchestrators Nomad job files and Amazon ECS task definitions
Platform as a service Cloud Foundry and Heroku Procfile
Platform as a service Fly.io, Railway, and Render configuration