Skip to main content
Coverage shows which manifests ZeroPath could fully resolve and where dependency data is incomplete.

Read and act on warnings

  1. In Assets → Repositories, open the repository and select the branch in Inventory → Overview. Check SBOM coverage for the manifest resolution percentage when it is available.
  2. To inspect the reason and file path, list the repository’s warnings. Common fixes include committing a supported lockfile and fixing registry access.
  3. Scan the same branch again after fixing the input. Check the new results before treating a missing package or finding as resolved.

Resolution coverage

Manifest resolution is the share of discovered manifests that ZeroPath fully resolved. A measured scan can have low manifest resolution if some of its dependencies could only be resolved partially or could not be resolved at all. If coverage has not been measured for the branch, run a new dependency scan.

Resolution fidelity

Resolution fidelity describes how ZeroPath obtained a dependency graph.
  • Deterministic — resolved from a committed lockfile (or a fully ==-pinned requirements.txt, which is treated as a lockfile-equivalent), so the inventory reflects the exact pinned versions your build is locked to.
  • Build-less — full transitive graph resolved directly from the manifest, no lockfile required, including native Ivy resolution. See Supported ecosystems for the per-ecosystem matrix.
  • Degraded (direct-only) — only your direct dependencies were resolved, for example because a required lockfile is missing or native resolution failed. Direct-dependency findings still surface; only the transitive tail is absent. This is the state to fix.
For Ivy, a failed resolution leaves both direct and transitive dependencies unscanned. Read the per-manifest warning; a degraded ecosystem summary does not guarantee direct-dependency coverage for every manifest.

Coverage warnings

Use an API key to call POST /api/v2/sca/listWarnings with organizationId and the repository IDs in repositoryIds. The response lists active warnings by default and includes the warning type, file path, and message. Use search to look for a manifest or lockfile path, and pass nextCursor as cursor to read the next page. Check the warning date against the scan you are investigating.
The first three warnings concern dependency resolution. Follow the per-manifest guidance to fix lockfiles, settings or registry access. The infrastructure variant often clears on retry; contact support if it persists. A zero dependencies anomaly is an advisory signal to re-check and re-scan, not necessarily a lockfile fix. The last three are transient data-source warnings that generally clear on the next scan on their own.

Lockfile coverage warnings

If a committed lockfile is unreadable or does not cover every declared dependency, some packages may be scanned at their declared versions. Affected findings can remain open. Regenerate the lockfile with your package manager, commit it with the matching manifests, and run a new scan. For pnpm workspaces, include the workspace lockfile and the manifests of the affected members.

Maven, Gradle, and sbt registry failures

If the warning names a Maven POM that could not be read, check that this coordinate’s POM was published and that the registry permits read access. If a build needs private libraries, parent POMs, BOMs, or plugins, follow Private Maven, Gradle & sbt Registries. Maven and Gradle share one connection; sbt uses a separate connection with an authentication realm and optional Ivy repository. A successful connection verifies the selected private package, not the whole build. Run a new scan, read the warnings for the affected manifests, and check that expected internal and transitive packages appear with resolved versions. Gradle and sbt can resolve transitives without a lockfile when native resolution succeeds. Alternatively, generate a supported lockfile in your build environment with registry access and commit it. When the manifest resolves from that lockfile, ZeroPath skips native build resolution. If the scan reports an error with a saved registry connection, correct the connection before retrying.

Ivy resolution failures

Like Maven, Ivy does not require a lockfile when native resolution succeeds. If it fails, standard and next-gen SCA show a Dependency resolution failed warning for the affected ivy.xml, rather than a Missing lockfile warning. Ivy requires a successful native resolution and has no direct-only fallback. Check ivy.xml, its colocated ivysettings.xml, included files and required properties. Ant targets are not executed, so properties calculated by a build must be supplied through Ivy settings or committed property files. Check access and stored credentials for any private repositories. Creating a lockfile does not resolve an Ivy configuration failure. See Supported ecosystems for supported Ivy settings.

Why findings don’t vanish on a failed scan

When a manifest can’t be resolved during a scan, ZeroPath carries forward the existing SCA findings for it instead of marking them resolved. This keeps a confirmed vulnerability from silently disappearing because of a transient resolution failure. A finding is auto-resolved only when its manifest was successfully analyzed and the vulnerability is genuinely gone.

Generate lockfiles before scanning

When the warning identifies a missing lockfile, generate and commit the supported file for that ecosystem. For JVM registry or build failures, check the registry setup first. The commands below produce the files ZeroPath looks for:
For npm/Yarn/pnpm, Maven, Ivy, and a fully ==-pinned requirements.txt (which ZeroPath treats as a lockfile-equivalent for deterministic resolution), dependencies can resolve without a lockfile — see Supported ecosystems.

Gradle and sbt lockfiles

For Gradle, first enable dependency locking in each project’s build.gradle or build.gradle.kts:
Then resolve the project’s dependencies and write the lockfile:
In a multi-project build, run the task for each relevant subproject, for example ./gradlew :app:dependencies --write-locks. Commit the generated gradle.lockfile files. Only configurations with locking enabled that the task resolves are included; see Gradle’s dependency-locking guide. For sbt, install sbt-dependency-lock in project/plugins.sbt, then generate and commit build.sbt.lock:
Generate these lockfiles in your build environment with access to the private registries your projects use.
The Assistant includes an SCA Coverage Autopilot playbook, under Configure → Playbooks. After each scan it reads the coverage warnings the scanner recorded and posts guidance for each affected manifest. You can also have it post a weekly coverage summary, optionally to a Slack channel you choose.

Operational notes

Inventories, alerts, and SBOMs are generated from the same sorted dataset, so diffs and reviews stay stable scan to scan.
Every scan captures a point-in-time inventory, enabling scan-to-scan diffs, SBOM exports, and retroactive investigations.
SCA captures the earliest git commit that introduced an affected manifest entry, so you can see how long a vulnerability has lived in your history.
Scans resume after interruptions, repeated failures are throttled, stale jobs are cleaned up, and completed inventories are reused where possible.