Troubleshooting: No Projects Detected

This article helps when a Vibgrate scan reports no projects or empty results. It is for developers who expected drift findings but saw none. For ecosystem coverage, see the supported manifests reference.

How detection works

A bare scan analyzes the current directory and the projects it detects there:

vg

Detection relies on recognizable manifests and lockfiles for each ecosystem. If none are found in the scanned tree, there is nothing to analyze.

Check the working directory

The most common cause is scanning the wrong directory — for example, a CI runner whose default directory is not your checkout. Point the CLI at the right place:

vg scan --cwd path/to/project

Check your exclusions

If your configuration or flags exclude the directory that holds your manifests, those projects disappear from results. Review excluded paths in your config (created by vg init) and any --exclude flags on the command line. Temporarily removing an exclusion is a quick way to confirm.

Confirm the ecosystem is supported

Vibgrate covers ~19 ecosystems including Node.js, .NET, Python, Java, Go, Rust, PHP, and Ruby. If your project uses one of these but is still not detected, confirm the manifest file is present and committed, not generated only at build time. See the supported manifests reference.

Confirm the CLI is healthy

Rule out an install or version problem:

vg --version

If needed, update and retry:

vg update

Still nothing?

Run from the project root with no extra flags to get the default behavior, then add scoping back one flag at a time until results appear. This isolates whether a flag or exclusion was hiding the project.

Related

• Supported manifests by ecosystem
• Configuration reference
• The vg init and vg scan command pages