Packaged software
Packaged sofware is software that is distributed through package managers that reorganize how software is delivered.
Each package maintainer has specific processes for remediating vulnerabilities and security issues, and each package has its own release cycle and versioning scheme. VulnPilot tracks packages and their vulnerabilities, and helps you understand how to remediate them.
Moreover, packages can both be parts of more complete software products, or can be an archive of several products.
Packages can be Linux distribution packages (for example Alpine apk, Debian/Ubuntu dpkg/apt, and RHEL-family rpm). They are a separate catalog from vendor products: a package is what your systems actually install and patch, including distribution-specific revisions and fixing versions from security advisories.
You can browse packages in the catalog (switch between Vendors and Packages on the catalog pages). You can also add packages to a watchlist so VulnPilot tracks advisories and vulnerabilities that affect them.
What a package represents
Each package row in VulnPilot describes one packaged software identity in a given ecosystem. Typical fields include:
| Concept | What it means |
|---|---|
| Name | Display name of the package (for example openssl). |
| Package manager | How the package is installed: apk, dpkg, or rpm. |
| Distribution / family | Ecosystem such as Alpine, Debian, Ubuntu, or RHEL family. |
| Distro name | Human-readable distribution label. |
| Package UID | Stable internal identity so similarly named packages on different distros stay distinct. |
| Aliases / source / upstream | Alternate names, source package name, or upstream project when known. |
| PURL / references | Optional Package URL and external references. |
| Status | Lifecycle status of the catalog row (for example active or obsolete). |
Packages with the same name on different distributions are not the same item. Alpine openssl and Debian openssl are tracked separately.
Package versions
A package has many versions. Each version is a shipped build for a release stream and may include:
- The full package version string as published by the distribution (including revision / patch level).
- An optional distro release (for example
3.18,bookworm,22.04,9) used as the primary frame for matching. - Architecture, epoch, and revision details when available.
- A version convention suited to that ecosystem (Alpine, Debian, Ubuntu, RPM, and related schemes) so VulnPilot can compare versions correctly.
Open a package from the catalog, then expand a version to inspect linked vulnerabilities.
Vulnerabilities and fixing versions
For a selected package version, VulnPilot shows advisory links to published vulnerabilities (and CVE identifiers when available). Relations include at least:
- Affected — this version is impacted by the vulnerability.
- Fixed in — this version includes the correction (the fixing package version from the advisory).
When a VulnPilot vulnerability ID or CVE is available, the UI links through to the vulnerability in the catalog. External advisory URLs remain available when the source provides them.
Packages versus products
| Products | Packages | |
|---|---|---|
| Origin | Vendor / CNA-oriented catalog software | Distribution maintainer artifacts |
| Typical identity | Vendor + product (± CPE) | Package manager + distro + name (± release) |
| Version framing | Product versions / branches | Distro release + package version / patch level |
| Use in watchlists | Track vendor products you run | Track OS packages you patch |
Use products when you care about upstream vendor software. Use packages when you care about what your Linux images and hosts actually install.
Frequently asked questions
Where do I find packages in the UI?
Open Products, Vendors, or Packages in the catalog and use the Products | Vendors | Packages tabs to switch. Package detail pages list versions and linked vulnerabilities.
Can I add packages to a watchlist?
Yes. In the watchlist create or edit workflow, open the products step and switch to the Packages tab. See Adding packages to a watchlist.
Do packages count toward my watchlist quotas?
Yes. Package members count toward the same watchlist item limits as products unless your plan documentation says otherwise. Contact us if you need higher quotas.