Widget Disable

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.

All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.

Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$widget_disable".

Detected usage of a non-sanitized input variable: $_POST[$this->dashboard_widgets_option]

$_POST[$this->dashboard_widgets_option] not unslashed before sanitization. Use wp_unslash() or similar

Detected usage of a possibly undefined superglobal array index: $_SERVER['HTTP_USER_AGENT']. Check that the array index exists before using it.

PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;

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.

Use of a direct database call is discouraged.

Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().

The "/vendor" directory using composer exists, but "composer.json" file is missing.

Tested up to: 6.7 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.

The plugin slug includes a restricted term. Your plugin slug - "wp-widget-disable" - contains the restricted term "wp" which cannot be used at all in your plugin slug.