I have recently managed to create a module on Drupal.org, following the entire process from sandbox, to project application, to full project.

After few weeks, my module lost the security shield and the following message is visible on the project page.

This project is not covered by the security advisory policy.
It may have publicly disclosed vulnerabilities. Use at your own risk!


I have gone through some of the documentation, such as Security advisory process and permissions policy, but I couldn't find an explanation.

Why does that message appear in the project page?
How can I resolve it?
How can I find what is wrong in my module?

  • ok, understood I have to do a stable release then as mentioned by @Pierre.Vriens
    – rjD
    Feb 21, 2017 at 7:20
  • Not in your screenshot
    – Jaypan
    Feb 21, 2017 at 7:22
  • 1
    The message has changed. Previously, the message only said something along the lines of 'modules with the shield are covered by the security advisory policy', whereas now it appears that modules without a full release now show the message in your screenshot.
    – Jaypan
    Feb 21, 2017 at 7:24
  • Much appreciated Pierre.Vriens & Jaypan
    – rjD
    Feb 21, 2017 at 7:31
  • A general note on this functionality: it's changing quickly as it is introduced. Please be patient and know that there is not an evil plot to discredit maintainers. Problems with this new feature will be sorted out shortly :)
    – greggles
    Mar 8, 2017 at 16:51

2 Answers 2


Only full releases get the security shield. Your screenshot only shows a dev version. I don't think the shield was removed from your module, as it wouldn't have had one in the first place since you don't have a full release.

To get the security shield, you'll need to release a full version (one not suffixed with -dev, -alpha or -beta).

** EDIT **

I have just discovered that an additional step needs to be taken in addition to creating a full release. Until recently, if a module was given a full-release, it automatically received the security advisory. However, I just promoted a module I've got from RC to a full release, and it did not receive the security advisory. Editing the module page now has an option that requires to module maintainer to opt into the security advisory.

Even having done so, my module still does not have the advisory shield, so I assume it now goes under some review from the security team before receiving it. This issue seems to support that assumption: https://www.drupal.org/node/2666584

--- Edit 2 ----

It turns out their was a bug in the system. I am already able to promote modules to drupal.org rather than the sandbox. With existing modules, when upgrading from D7 -> D8, modules were automatically given the shield when I released a full version. However the module I mentioned above did not have a D7 version, and when I promoted it to a full release it didn't receive the shield. After waiting two weeks for approval I finally contacted the security team, and they looked into it and found a bug in the caching system, and fixed it.

So it appears that the original information I gave - that you just need to release a full version, and have opted into security advisory coverage, is correct.

Here's a screenshot of the module edit page. Screenshot of module edit page

  • where on module pages is that option? Eiher I can't find it, or I don't have such option on my module's page. Can you add a screenprint and/or more details where exactly you found that? Could it be for D8 only (mine is for D7)? PS: "where" on that linked issue did you see that "support" (that is a huuuuuuuuge issue ...) Feb 24, 2017 at 19:48
  • I added an screenshot to my post that shows the option. I'm not sure if it's a D8 only thing - I think it's probably not. But I think it's only for new modules, and I suspect the option only appears if you've released a full-version of your module.
    – Jaypan
    Feb 25, 2017 at 3:49

You need to create an official release, for at least 1 version of Drupal core that is supported. In your case, for D7, like a 7.x-1.0 version of your module. Shortly after doing so, your module will have the security shield.

If you want, have a look at modules such as the Conditional Rules module, used in over 11K Drupal 7 sites. It has the same message shown on its project page also.

Drupal core criteria

  • "Only full releases get the security shield" (as in the accepted answer) may need some refinement: have a look at the Support Ticketing System module, which does have a full release for D6 (which is no longer supported). But it does NOT have the security shield either.
  • If a module does have an official release for at least 1 version of a supported Drupal core version (eg: for D7), then the security shield will not be removed by adding a dev, alfa, beta or rc version (with no official release yet) for another supported Drupal core version (eg: for D8). For a sample of this, have a look at the Rules module. Note however that in this case the D7 version has an extra (green) shield that is not shown for the D8 version of it.

More info

For way more details on this, refer to these issues:

How to create an official release

Head over to your https://www.drupal.org/project/myproject/git-instructions (whereas you replace myproject with your module name). Near the bottom of it, you'll find detailed instructions about Creating Releases. More specifically you should do what's mentioned within Tag for a stable release there, which is like so:

git checkout 7.x-1.x

git tag 7.x-1.0

git push origin tag 7.x-1.0

Once you've pushed the properly formed tag or branch, see Creating a project release for directions to actually create the release node.

Bonus tips

  • If you're not ready yet to create an official release, you can always add some note on your project page like "Note: as the module maintainer, I'm not aware of any publicly disclosed vulnerabilities".
  • IMO "Use it at your own risk!" applies NOT only to contributed modules for which the security shield is NOT shown.

Related article

Drupal Security Shield For Contributed Modules,What That Means? (Credits: zhilevan)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.