sajidhussain

Instead of asking for both an email and a username on registration, this plugin lets you ask for email only, and uses that as username as well. Since the password is automatically generated and emailed to the user, this allows for sign-up form with a single form field: email.
For users that registered with different username and email address before this plugin was installed, their username and email address will be interchangeable on login.
The plugin offers a shortcode, [NP-registration], to add the registration form to a post or page.
Note: This plugin has not been tested with WP versions older than to 3.1.5. It should work with some older versions, but we can not guarantee it. However, if you are running an older version of WordPress, there are some very compelling arguments why you should consider upgrading. If you need help, there is plenty of free help to be found on WordPress.org, and Next Page, the authors of this plugin, offer a paid WordPress maintenance service.

Login Tweaks by Next Page

Use email as username to allow for single-field signup. Adds shortcode for adding registration form to post.

Scott Reilly

This plugin allows you to restrict the usernames that new users may use when registering for your site.
If open registration is enabled for your site (via Settings -> General -> Membership (“Anyone can register”)), WordPress allows visitors to register for an account on your blog. By default, any username they choose is allowed so long as it isn’t an already existing account and it doesn’t include invalid (i.e. non-alphanumeric) characters.
Possible reasons for wanting to restrict certain usernames:
<ul>
<li>Prevent usernames that contain foul, offensive, or otherwise undesired words</li>
<li>Prevent squatting on usernames that you may want to use in the future (but don’t want to actually create the account for just yet) (essentially placing a hold on the username)</li>
<li>Prevent official-sounding usernames from being used (i.e. help, support, pr, info, sales)</li>
<li>Prevent official username syntax from being used (i.e. if all of your administrators use a prefix to identify themselves, you don’t want a visitor to use that prefix)</li>
<li>Prevent spaces from being used in a username (which WordPress allows by default)</li>
<li>Require that a username starts with, ends with, or contain one of a set of substrings (i.e. “support_”, “admin_”)</li>
<li>Require a minimum number of characters for usernames</li>
<li>Limit usernames to a maximum number of characters</li>
</ul>
When attempting to register with a restricted username, the visitor will be given an error notice that says: 
ERROR: This username is invalid. Please enter a valid username.
NOTE: This plugin does not put any restrictions on usernames that the admin chooses for users when creating user accounts from within the WordPress admin. This only restricts the names that users choose themselves when registering for your site.
SPECIAL NOTE: Many membership plugins implement their own user registration handling that often bypasses checks (and hooks) performed by WordPress. As such, it is unlikely that the plugin is compatible with them without special plugin-specific amendments.
Compatible with Multisite and BuddyPress as well.
Links: <a href="http://coffee2code.com/wp-plugins/restrict-usernames/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/restrict-usernames/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/restrict-usernames/" rel="nofollow ugc">GitHub</a> | <a href="http://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
The plugin exposes one filter for hooking. Typically, customizations utilizing this hook would be put into your active theme’s functions.php file, or used by another plugin.
c2c_restrict_usernames-validate (filter)
The ‘c2c_restrict_usernames-validate’ hook allows you to add your own customized checks for the username being registered. You can add additional restrictions or override the assessment performed by the plugin.
Arguments:
<ul>
<li>$valid (boolean): The assessment by the plugin about the validity of the username based on settings. True means username can be used.</li>
<li>$username (string): The username being registered.</li>
<li>$settings (array): The plugin’s settings.</li>
</ul>
Example:
<pre><code>/**
 * Add custom checks on usernames.
 *
 * Specifically, prevent use of usernames ending in numbers.
 *
 * @param bool $valid True if the username is valid, false if not.
 * @param string $username The username.
 * @param array $options Plugin options.
 */
function my_restrict_usernames_check( $valid, $username, $options ) {
 // Only do additional checking if the plugin has already performed its
 // checks and deemed the username valid.
 if ( $valid ) {
 // Don't allow usernames to end in numbers.
 if ( preg_match( '/[0-9]+$/', $username ) ) {
 $valid = false;
 }
 }
 return $valid;
}
add_filter( 'c2c_restrict_usernames-validate', 'my_restrict_usernames_check', 10, 3 );
</code></pre>

Restrict Usernames

Restrict the usernames that new users may use when registering for your site.

Login Tweaks by Next Page vs Restrict Usernames