🌪️ Prioritize OSS risks with the Used in code insight, now GA
We’ve made it easier to focus on real risks in your code with our latest feature, the Used in code insight.
This feature distinguishes between vulnerable dependencies that are actively imported versus those that remain dormant in your project files without affecting your application. This helps you spend less time triaging and gives you more time to prioritize the risks that matter.
To address these risks, apply the Used in code filter in the SCA Risks Page.
Apiiro shows the Used in code insight for directly imported dependencies and for sub-dependencies when one or more top-level (direct) dependencies are imported into the code.
To see the supported dependency types, package managers, and languages for the Used in code insight, refer to the SCA support matrix for this feature.
For more info on the Used in code insight, see OSS Insights and Target imported dependencies
