Dependencies with no Version Specified

The tile labeled Dependencies No Version Specified provides a count of all dependencies (direct and transitive) which do not have the version specified. For more information on how dependencies are identified, please see Dependency Detection.

Go projects should always have a commit specified in the glide.lock file. Therefore, Go projects should always have zero unversioned dependencies.

Governance:

The Dependency no Version rule governs the pass/fail status of the scan results. When this rule is enabled in the governing ruleset, the analysis will only pass if all dependencies have a version specified.

Tile Statuses:

Passing: All of the project's dependencies include a version, and the governing ruleset requires that dependencies have a version specified.

Failing: One or more of the project's dependencies do not specify a version and the governing ruleset requires that dependencies have a version specified.

Warning: The scan has been completed, the governing ruleset does not require that dependencies have a version specified, and dependencies without a specified version were detected.

Not Evaluated: The scan has been completed, the governing ruleset does not require that dependencies have a version specified, and no dependencies without a specified version were detected.

Error: An error occurred during the scan or analysis. Selecting the tile will provide information on the cause of the error.