Password Validator VS Password Compat

Compare Password Validator vs Password Compat and see what are their differences.

Password Validator

Validates passwords against PHP's password_hash function using PASSWORD_DEFAULT. Will rehash when needed, and will upgrade legacy passwords with the Upgrade decorator. (by jeremykendall)

Password Compat

Compatibility with the password_* functions that ship with PHP 5.5 (by ircmaxell)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
Password Validator Password Compat
- 1
146 2,149
- -
0.0 0.0
about 6 years ago 3 months ago
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Password Validator

Posts with mentions or reviews of Password Validator. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Password Validator yet.
Tracking mentions began in Dec 2020.

Password Compat

Posts with mentions or reviews of Password Compat. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-25.
  • WordPlate: WordPress on Composer with sensible defaults
    9 projects | | 25 Feb 2023
    > Same for WordPress.

    Not as much - WP favours backwards compatibility (or is it laziness?) even when doing so impacts security.

    Another problem is that the environments Wordpress targets are inherently vulnerable - while it's not WP's fault directly, they do nothing to warn people against using them nor outright stop supporting broken, insecure configurations.

    > There are multitudes of comments that specifically single out WP in the post's comment thread. Including this very thread that you are on.

    I was talking about publicized data breaches in general. But if we specifically talk about CMSes, I'm not sure anything else beats Wordpress and similar PHP-based CMSes of that era when it comes to not just the amount of vulnerabilities, but especially the nature of them - the same, dumb, basic problems resolved in every other language (including modern PHP with a framework such as Laravel) repeated over and over again.

    > WHERE is that objective study that compares WordPress with other software in regard to vulnerabilities

    Someone posted the following excerpt of the Wordpress codebase, which appears to be some custom attempt at simulating SQL query parameterization instead of using the actual, database-driver-provided function. If this is indeed the purpose of that function and it is indeed used, then I'm not sure there is any valid excuse for this in today's day and age.

    Someone else mentioned password hashing still relying on MD5 - if that is actually true, I'm not sure that is excusable either? I haven't done PHP for many years now, but surely even if the native functions aren't available, couldn't they use a "polyfill" such as ?

    I'm sure there are many other issues but frankly the first one should be enough for any competent developer to run away.

    > No it doesnt. Dont make up falsities. PHP executes files how you configure it to.

    I was with you until this, but now I think you're arguing in bad faith.

    Yes, if you want to be pedantic, PHP and your web server execute files like how you configure them to. In practice, the environment where the vast majority of Wordpress sites are deployed (your typical shared hosting environment) will execute anything that ends with .php and is in the web root.

    This is inherently a legacy PHP problem (which WP encourages by supporting it) - no other language that I know of does this by default. If I accidentally store a malicious file in Python, Ruby, Node.js, etc applications, the worst that will happen is that I serve it back. At no point what so ever the server itself will execute that file.

    Yet in the PHP environments Wordpress targets, this is a massive issue which means every single feature handling file uploads (both in WP core and any plugins) should anticipate your server's misconfiguration (maybe it's not limited to .php files, but .html files too?) and try to protect against it, eventually failing and then you get yet another Wordpress vulnerability.

What are some alternatives?

When comparing Password Validator and Password Compat you can also consider the following projects:

Password Policy - A password policy enforcer for PHP and JavaScript

weakpass - Weakpass collection of tools for bruteforce and hashcracking