Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
22 Jan 2026 at 12:47 UTC
Updated:
6 Feb 2026 at 11:11 UTC
Jump to comment: Most recent
Comments
Comment #2
m4th3o commentedComment #3
avpadernoThank 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.
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.
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.
Comment #4
avpadernoI do not have time for a full review.
The license should be the same license used by Drupal core. The license file used for this project is incomplete.
Comment #5
m4th3o commentedFixed License
Comment #6
bbu23Adding some things I noticed by taking a very quick look:
- Missing schema for the configuration object provided by the module in
config/install.- New modules, which are compatible with Drupal 10 and higher versions are expected to include type declarations in property definitions, and use property promotion. Update all classes.
- I see some bad line indentation, run your code through PHPCS and fix all errors and warnings. I also recommend adding gitlab-ci for automated checks.
- For a new module that aims to be compatible with Drupal 10 and Drupal 11, I would rather implement hooks as class methods as described in Support for object oriented hook implementations using autowired services.
- I recommend adding tests.
- Implement plugins as PHP Attributes instead of PHP Annotations as described in Attribute-based plugins.
Comment #7
vishal.kadam1. The project is missing a README.md file that follows the template suggested in README.md template.
2. FILE: social_post_instagram.module
The usual description for a .module file is “Hook implementations for the [module name] module”, where [module name] is the module name given in the .info.yml file.
The description for this hook should also say for which form that hook is implemented, either by indicating that with the name of the class that implements the form (namespace included) or the form ID (which is usually indicated by
getFormId()).3. FILE: src/InstagramPostAuthManager.php
FILE: src/Controller/InstagramPostController.php
FILE: src/Plugin/Action/PostToInstagram.php
FILE: src/Services/InstagramApiService.php
FILE: src/Settings/InstagramPostSettings.php
New modules, which are compatible with Drupal 10 and higher versions are expected to include type declarations in property definitions, and use constructor property promotion.
4. FILE: src/Form/InstagramPostSettingsForm.php
With Drupal 10 and Drupal 11, there is no longer need to use #default_value for each form element, when the parent class is ConfigFormBase: It is sufficient to use #config_target, as in the following code.
Using that code, it is no longer needed to save the configuration values in the form submission handler: The parent class will take care of that.
For this change, it is necessary to require at least Drupal 10.3, but that is not an issue, since Drupal 10.2.x is no longer supported.
Comment #8
m4th3o commented