Problem:
Sometimes 0 dependencies are found when scanning a maven pom.xml file when running snyk in CLI mode.
Discussion:
There are a number of reasons a dependency may not be picked up:
- Un-initalized environment variable in the pom.xml file (for instance '${VERSION}')
- Scoped or private registry in the file
Resolution:
Ensure environment variables are initiated before running snyk.
Ensure snyk can access the private registries.