Opening a dependency audit you have already run is Free, and it does not look anything up online again. Your account and workspace access are checked when you are online; results that were confirmed earlier stay readable offline.Running a fresh audit uses one local project action when it produces a usable result. Looking up package versions and vulnerabilities online still needs your permission first. See Free allowances.
Opening it
Run Iris Code: Open Dependents Table from the command palette. The table compares each package with its public registry, the online catalogue where the package is published, and against the OSV.dev vulnerability database.Where it reads from
- npm -
package.json - Go modules -
go.mod - Python -
requirements.txtandpyproject.toml - RubyGems -
Gemfile.lock, withGemfileand.gemspecfallbacks - NuGet -
.csproj,Directory.Packages.props,packages.lock.json, andpackages.config - Cargo -
Cargo.lock, withCargo.tomlas the fallback for libraries, which conventionally do not commit a lockfile - Maven and Gradle -
pom.xmlandbuild.gradle/build.gradle.kts, including Gradle version catalogues ingradle/libs.versions.toml
Versions come from your lockfile
A manifest is a file that lists the packages your project asks for. A lockfile records the exact versions selected, including packages brought in by other packages. A manifest range like"express": "^4.18.0" does not tell you which version is installed. The lockfile does, so it is read in preference when one is present:
- npm -
package-lock.json(v1-v3) - pnpm -
pnpm-lock.yaml - yarn -
yarn.lock(classic and Berry) - Python -
poetry.lockandPipfile.lock - RubyGems -
Gemfile.lock - NuGet -
packages.lock.json - Cargo -
Cargo.lock
- RubyGems and Cargo lockfiles include every package, including those brought in by other packages.
- NuGet without
packages.lock.jsonchecks only the packages your project declares directly. - Maven and Gradle declarations are read from the build files, not from a full list of installed packages.
Monorepos
A monorepo is one repository holding several projects. Workspace members declared through npm or yarn workspaces, or inpnpm-workspace.yaml, are found automatically, and their dependencies are combined into a single view, with a repeated package listed once. Internal workspace: / file: / link: dependencies are excluded, since they are your own packages rather than third-party ones.
What the table shows
For each package, the table displays the installed version, the latest available version, and any known CVEs from the OSV.dev database:
Each advisory shows a severity badge, the advisory id, a confidence label, and the fixed-in version where one exists. A package reported in the OpenSSF malicious-packages feed (an advisory id starting
MAL-) is badged malicious rather than by severity, because those reports carry no severity score. To stop such a package being added in the first place, see the package guard.
A CVE is a public identifier for a known security vulnerability. Advisories describe the affected versions and, where known, which version fixes the problem.
Confidence labels
A count of vulnerabilities is not much use on its own; what matters is which ones you can fix. Every advisory carries a label saying how you can act on it:Unverifiable advisories are never shown
An advisory record without an id or severity that can be checked is dropped rather than shown, and the footer says how many were skipped. Duplicate records describing the same underlying advisory are collapsed into a single row. If a lookup fails outright, through a network error or a registry outage, that package is marked not checked rather than assumed clean. “No vulnerabilities found” and “the check did not complete” mean different things, and the table distinguishes them.The sidebar badge
The Dependencies section of the Workspace tab shows a summary of your last scan: green when it came back clean, otherwise the number of vulnerable packages and the highest severity found. It reads only from the local cache, so opening the sidebar never triggers a network request on its own. Refresh it from the Dependents Table, or by runningiris deps.
Caching
Results are cached for 24 hours, so reopening the panel is immediate. The cache is kept per user, under~/.iris/cache/, and never inside the project: a cache file committed to a repository could otherwise decide what a scan reports. Iris Code does not write into your project or its .gitignore for this.