In the last three posts, I’ve talked about libraries for WordPlugins that I find to be extremely helpful in writing high-quality codebases.
If you’ve not been following along, you can either catch-up by reading the previous posts:
Or you can just review the list of tools I’ve listed thus far:
This post will wrap up the series with the final set of tools that we typically use when building solutions for others.
Libraries for WordPress Plugins, The End
The purpose of this series has been to share the tools, utilities, and libraries for WordPress plugins that I’ve found – through others and through experience – to help write high-quality code before even committing it to Git.
So here’s an explanation of the final two libraries.
From the project’s homepage, the purpose of this library is as follows:
But what’s this mean exactly?
I think it’s fair to say that most developers want to write secure code, but it’s tough to be aware of all of the various vulnerabilities that exist (especially when they change day-to-day).
That’s where Security Checker comes into play:
The SensioLabs Security Checker is a command line tool that checks if your application uses dependencies with known security vulnerabilities. It uses the SensioLabs Security Check Web service and the Security Advisories Database.
Just like the other libraries mentioned in this series, this is one that hooks into the commit process and analyzes your code against the aforementioned databases.
Using These in Projects
This wraps the full list of tools that I set out to cover when writing this series; however, for some, it still raises the question of how to hook these into WordPress-based projects.
So in an upcoming post, I’ll walk through exactly that.