Custom Login allows you to easily customize your admin login page, works great for client sites!
Prioritized issue groups from the latest Plugin Check scan
Maintainability
96
7 issue groups
Security
37
4 issue groups
I18n
11
2 issue groups
Repo Compliance
3
3 issue groups
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$all_user_ids".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$button_text'.
Sample message
A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
$_GET['_wpnonce'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Detected usage of a non-sanitized input variable: $_GET['_wpnonce']
Sample message
Processing form data without nonce verification.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "custom_login/login_footer_html".
Sample message
load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "Factory::PREFIX . 'actions'".
Sample message
Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead
Sample message
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Sample message
Mismatched "Tested up to": 7.1.0 != 7.1. The "Tested up to" value in the readme file must match the "Tested up to" value in the plugin header. If the plugin header has a "Tested up to" value, it will override the readme value, which can cause confusion.
Sample message
The "/vendor" directory using composer exists, but "composer.json" file is missing.
Sample message
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Sample message
Mismatched Requires at least: 6.7 != 6.4. "Requires at least" needs to be exactly the same with that in your main plugin file's header.
Potential connections found in static code analysis.
Outbound calls
300
External assets
0
Incoming endpoints
0
No external asset domains detected.
No public endpoints detected.
2 score snapshots
v5.1.3
42
Latest
v5.1.2.2
42
Score
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 42 | 147 | 36 | 111 | v5.1.3 | 2.0.0 |
| 42 | 152 | 36 | 116 | v5.1.2.2 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.