[1.0.x] Ez Page Builder

Thank you for applying!

Please read Review process for security advisory coverage: What to expect → for more details and Security advisory coverage application checklist → to understand what reviewers look for. Tips for ensuring a smooth review → gives some hints for a smoother review.

The important notes are the following.

• If you have not done it yet, you should run phpcs --standard=Drupal,DrupalPractice on the project, which alone fixes most of what reviewers would report.
• For the time this application is open, only your commits are allowed.
• The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status will not be changed by this application; once this application is closed, you will be able to change the project status from Not covered to Opt into security advisory coverage. This is possible only 14 days after the project is created.
  Keep in mind that once the project is opted into security advisory coverage, only Security Team members may change coverage.
• Only the person who created the application will get the permission to opt projects into security advisory coverage. No other person will get the same permission from the same application; that applies also to co-maintainers/maintainers of the project used for the application.
• We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the project name and the branch to review.

To the reviewers

Please read How to review security advisory coverage applications → , Application workflow → , What to cover in an application review → , and Tools to use for reviews → .

The important notes are the following.

• It is preferable to wait for a project moderator before posting the first comment on newly created applications. Project moderators will do some preliminary checks that are necessary before any change on the project files is suggested.
• Reviewers should show the output of a CLI tool → only once per application.
• It may be best to have the applicant fix things before further review.

For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues → .

Usually, after reviewing a project, we allow the developer to opt projects into security advisory coverage. This project is too small for us and it doesn't contain enough PHP code to really assess your skills as developer.

Have you created any other project on drupal.org (module, theme, distribution) we could instead review? The project needs to have most of the commits (preferable all the commits) done by you.

Yes I have done this before.
some of my contributed modules are :
https://www.drupal.org/project/custom_node_breadcrumbs →

and these are some where I work as a mainatiner:

https://www.drupal.org/project/rules_http_client →
https://www.drupal.org/project/ezcontent_publish →
https://www.drupal.org/project/ezcontent_demo →

A project that can be used for these applications needs to have sufficient PHP code (a single plugin class is not sufficient) and have most of the commits (but preferably all the commits) done by you.

If you have a project which matches those criteria, please edit the issue summary and change it to contains a short description of that project and a link to the project page.

I have items that meet the specified criteria. Please inform me of any requirements:

https://www.drupal.org/project/ezcontent →

EzContent is a Drupal installation profile that addresses common content management pain points and accelerates CMS implementations.

https://git.drupalcode.org/project/ezcontent/-/tree/3.0.x-dev

https://www.drupal.org/project/ezcontent_api →

This module adds JSON API functionality to EZContent profile.

https://git.drupalcode.org/project/ezcontent_api/-/tree/2.3.x?ref_type=h...

https://www.drupal.org/project/ezcontent_publish →

This EzContent Publish module provide additional feature on top of ezcontent profile for content editor's.

https://git.drupalcode.org/project/ezcontent_publish/-/tree/2.1.x?ref_ty...

@abhinesh project listed in #7 are already covered by the security advisory policy.

Please go through comment #6

If you have a project which matches those criteria, please edit the issue summary and change it to contains a short description of that project and a link to the project page.

Furthermore, the project used for an application must have most of the commits (preferable all the commits) done from the applicant in at least a branch.