PayU GPO Payment for WooCommerce

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

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "add_payu_gateways".

Processing form data without nonce verification.

In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.

Processing form data without nonce verification.

Detected usage of a possibly undefined superglobal array index: $_POST['payu-google-token']. Check that the array index exists before using it.

$_GET['key'] not unslashed before sanitization. Use wp_unslash() or similar

Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.

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.

Mismatched text domain. Expected 'woo-payu-payment-gateway' but got 'woocommerce'.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"[$param] is not set."'.

Detected usage of a non-sanitized input variable: $_GET['key']

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

Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "WC_PAYU_PLUGIN_PATH".

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

wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.

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.

Plugin name "PayU GPO Payment for WooCommerce" is different from the name declared in plugin header "PayU Payment Gateway for WooCommerce".

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

Tested up to: 6.9 < 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 - "woo-payu-payment-gateway" - contains the restricted term "woo" and cannot be used to begin your plugin slug. We disallow the use of certain terms in ways that are abused, or potentially infringe on and/or are misleading with regards to trademarks. You may use the term "woo" elsewhere in your plugin slug, such as "... for woo".