Dev releases are not covered by the Drupal security policy, so should be grouped with the other modules that are not opted in. Dev versions (e.g. 1.0.x-dev) are never listed as releases in the release history XML, so $found stays FALSE and they fall into the "Unknown / Unable to find release information" bucket instead of "Not opted-in".

The fix is to detect dev versions before making the API call and short-circuit them straight to $not_covered

Issue fork msacr-3581158

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

nicrodgers created an issue. See original summary.

nicrodgers’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.