feat: introduce application dependency discovery for container rootfs#26
Merged
PrasanthYT merged 1 commit intomainfrom Mar 4, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This change introduces application dependency discovery within container images.
The container engine now scans the reconstructed root filesystem for common dependency manifests and extracts application-level dependencies using the existing SCA parsing logic.
Supported Manifest Types
The scanner searches the container filesystem for the following files:
These files represent dependencies for Node, Python, and Rust applications.
Parser Reuse
Existing dependency parsers from the SCA engine are reused to avoid code duplication.
Supported ecosystems include:
Dependency Extraction
Each discovered dependency is converted into the internal dependency representation used by the scanning engine.
Example:
Dependency Merging
The container engine now merges dependencies from two sources:
Both sets are combined into a unified dependency list.
Deduplication
Dependencies are deduplicated using the composite identity:
This ensures deterministic results and prevents duplicate vulnerability checks.
Updated Container Pipeline
The container scanning flow now becomes:
Impact