Stable release with Drupal's security advisory policy

Created on 13 December 2019, about 5 years ago
Updated 5 December 2024, 13 days ago

Hi Guys,

would you mind checking the opt-in so we can have coverage by Drupal’s security advisory policy. With certain Security Team's its often an easier "sell" when evaluating modules. Often certain security teams are scared away when they see the warning:

This project is not covered by Drupal’s security advisory policy.

For that we need a stable release. What's blocking us here for a stable release?

📌 Task
Status

RTBC

Version

2.0

Component

Miscellaneous

Created by

🇩🇪Germany Peter Majmesku 🇩🇪Düsseldorf

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇫🇷France Grimreaper France 🇫🇷

    Hi,

    There is a stable release 2.0.0 and the project had opt-in into security advisory policy.

    I think a maintainer can mark this issue has fixed.

Production build 0.71.5 2024