Components
A new vulnerability lands in a popular library, and someone asks if you use it. Answering that shouldn't mean searching forty repositories by hand.
Components is the inventory behind your findings: everything your resources are made of and use, across all of them. It answers "where do we use this?" even when no finding exists yet.
Prerequisites
resources:read.- At least one completed scan of code or an image. Components appear once those are scanned.
The four groups
Open Components in the left rail. Each tab is a group with its own columns.
| Group | What it lists | Columns |
|---|---|---|
| Packages | Every package the current versions of your repositories and images contain | Package, Ecosystem, Versions in use, Licenses, Used by, Findings |
| Crypto | Algorithms, protocols, certificates and keys your code and images use or ship | Crypto asset, Kind, Details, Used by, Findings |
| AI | Models, agents, tools, MCP servers and model files | Component, Kind, Details, Versions in use, Used by, Findings |
| Privacy | Third-party SDKs that receive personal data, and which data they get | Package, Versions in use, Third parties, Personal data sent, Used by |
Answer "do we use this?"
- Open the Packages tab.
- Type the package name in the search box.
- Select the row to open its detail panel.
The panel shows:
| Section | What you learn |
|---|---|
| Identity | Exactly what this component is |
| Versions in use | Each version the current versions of your resources use |
| Used by | Resources whose tracked refs' current snapshots contain it |
| Open findings | The worst open findings on it |
| Links | What it uses or what uses it, such as a certificate's algorithms or an agent's model |
| Attributes | The details as the scans reported them |
That's your answer: which versions, in which resources. It covers the refs you track and nothing else, so an untracked branch won't appear. See Tracked refs.
Filter
| Filter | Groups | Use it to |
|---|---|---|
| Kind | Crypto, AI | Separate certificates from keys, or models from tools |
| Ecosystem | Packages, Privacy | Stay within npm, pypi, golang and so on |
| License | Packages, Privacy | Find every package under one license |
| Used in | All | Stay on one resource |
| Connection | All | Stay within one integration connection |
| Open findings | All | Show only components with, or without, findings |
The License filter is a quick way to answer legal questions. Pick an AGPL license and you have the list you were going to be asked for.
Components on a single resource
Every repository and image has its own Components tab. It shows what the newest scan found inside that resource, or the scan you pick beside Rescan. It adds attestations, and on an image it shows each platform's base image, what it ships, and how far behind its tag it is.
Use the rail page for questions across everything, and the resource tab when you're looking at one thing.
Components are facts, not problems. A package with no findings still appears here, which is exactly why this page helps when a new vulnerability is announced.
Try this next
Open the Crypto tab and set Kind to Certificate. Details include who issued each one and when it expires. A certificate expiring in a repository nobody watches is an outage waiting for a date, and you can see it from here.