Possible compliance with Drupal’s Security Advisory Policy

+1 to opt into security coverage.
You can do this on the project page if the project is "old" enough

Hi @jigarius and @mschudders,

Could you please review the code and provide feedback? Additionally, I’d appreciate any guidance on aligning it with Drupal’s Security Advisory Policy.

Looking forward to your insights.

According to the Which Projects are Covered? → section of the Security advisory process and permissions policy page:

Project maintainers may opt into security advisory coverage when they meet the requirements:

• A maintainer with “write to VCS access” has applied to have the "vetted" role, and received it.
• The project is a full project, not sandbox projects.
• There are no known security issues, open issues tagged “security” for the project.
• New projects must wait 10 days before opting in.