ZeroPath adds the fallback partition automatically during conversion. It has no directory paths of its own; its scope is the paths that no named partition covers.
Partitions are configured by you. The applications shown in threat models and issue filters are discovered from code, and a partition can contain more than one application.
Create partitions
Start with a repository already connected to ZeroPath. Creating partitions or changing their directory paths requires Create Repositories permission.- Open Assets → Repositories → Monorepos, then select Create monorepo.
- Select the repository to convert.
- Give the first partition a Partition Name and one or more Directory paths.
- Use Add Another Partition for each additional group of directories.
- Click Convert to Monorepo. The fallback is added alongside your named partitions.
- Open each partition’s repository page to review its scanner settings, configure its schedule, and start a scan.
Directory path rules
- Use paths relative to the repository root, ending in
/, such asapps/web/. - A partition can include several directories.
- Paths are directory prefixes. File names, glob patterns such as
**/*.ts, absolute paths, and..are not supported. - Different partitions cannot overlap:
apps/andapps/web/cannot belong to separate partitions.
How scans use partitions
Full scans
Each partition runs a separate scan. The scanner can read the whole repository to understand imports and shared code, so scan time still includes work outside the partition’s directories.- Code findings. A named partition can report a finding if the location
or the start of its data flow is in that partition. For example, API can
report a flow that starts in
services/api/and reachespackages/shared/. The fallback uses the reported location. - Dependency findings. A named partition can report a finding if it contains the package usage or the declaring manifest. For a shared root manifest or lockfile, a finding follows the package usage when ZeroPath identifies it in a named partition. Otherwise it goes to the fallback if one exists. Without a fallback, named partitions can report unused shared dependencies in their scope.
- Repository-wide end-of-life findings. These go to the fallback, or to each named partition if there is no fallback.
Pull requests
Each partition’s PR scan, including the fallback’s, reviews only the changed files that partition owns and skips PRs that change none of them. On GitHub, changed files select which partitions receive scans; a PR touching both Web and API can trigger a scan for each. On GitHub, if a later push changes only another partition’s files, the checks can carry earlier findings forward to the new commit. Partitions sharing a ZeroPath check can keep it failing while a partition has an unresolved failing result. Open the check to see which partition is blocking it. In the example above, a GitHub PR changing onlypackages/shared/ routes to the fallback. It does not automatically trigger scans for every service that imports that code. Run full scans of the affected partitions when you need to check those services after a shared-code change.