Software inventory

Compliance & Audit → Software (/gravity/inventory/software) lets you search installed software by package name across every enrolled fleet agent in your organization, and flags packages that have reached end of life. This page covers that fleet-level software view specifically; for the broader inventory of discovered cloud resources (Compliance & Audit → Inventory), see Compliance → Inventory - it’s a related but different picture: that one is about what’s running in your connected cloud accounts, this one is about what’s installed on hosts running the fleet agent.

What’s collected

An agent with the inventory-scanning capability granted collects a full list of installed packages roughly every 24 hours (the first scan runs about 10 minutes after the agent starts, after the initial patch scan). For each package, the agent records:

• Name and version
• Source (which package manager or registry it came from)
• An end-of-life status, where applicable: critical, warning, or info

End-of-life status is determined at collection time by checking the package against a known end-of-life dataset - a package with no known end-of-life data simply has no status shown, not a false “OK.”

This requires the inventory-scanning capability to be granted on each agent (Fleet → Agents → Grant Capability → Inventory: Scan) - an agent without it never uploads its package list, so it won’t appear in a search here even though it’s otherwise connected and reporting.

Searching

1. Open Compliance & Audit → Software.
2. Enter a package name and search.
3. Results list every matching package found across your fleet, one row per host.

Each result row shows:

Column	Meaning
Host	The agent’s hostname
OS	The host’s operating system
Package	The matched package name
Version	The installed version on that host
Source	Which package manager or registry it came from
EOL Status	Critical, warning, or info, if the package has known end-of-life data
Collected	When that host’s inventory was last scanned

This is a cross-fleet search by package name - it’s the fastest way to answer “which of my hosts still have <package> installed” after a disclosure, without opening each host’s own record individually.

Note

If a package you expect to find doesn’t turn up, check three things: the package is actually installed on at least one enrolled host, that host’s agent has the inventory-scanning capability granted, and its most recent scan has actually completed (scans run roughly every 24 hours, starting about 10 minutes after the agent connects).

Beyond a name search

This page is deliberately a search, not a browsable catalog - it’s built to answer “where is <package> installed” quickly, not to list everything installed on every host. If you need a recurring, scheduled check against your fleet that goes beyond a package name - for example, checking a specific container image tag or a service’s running status - see Custom probes, which run your own defined command across every enrolled agent on a schedule.

Search results are scoped to your own organization - you’ll only ever see packages installed on agents belonging to organizations you’re a member of, never another customer’s fleet.

What’s next

• Patch management - outdated packages and available updates
• Compliance → Inventory - the broader cloud-resource inventory
• Vulnerabilities - vulnerability findings elsewhere in the platform
• Agent policies - autonomy levels and custom probes (the inventory capability is granted on Fleet → Agents)