Require Post Category Security & Risk Analysis

wordpress.org/plugins/require-post-category

Require users to choose a post category before updating or publishing a post.

1K active installs v2.1 PHP + WP 5.5+ Updated Apr 5, 2024
categorypostrequiretagstaxonomy
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Require Post Category Safe to Use in 2026?

Generally Safe

Score 85/100

Require Post Category has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 2yr ago
Risk Assessment

The "require-post-category" v2.1 plugin exhibits a very strong security posture based on the provided static analysis data. There are no identified attack vectors such as AJAX handlers, REST API routes, shortcodes, or cron events. Furthermore, the code signals indicate a complete absence of dangerous functions, raw SQL queries, file operations, external HTTP requests, and critical security checks like nonces and capability checks, all of which is excellent. Taint analysis shows no identified flows with unsanitized data, reinforcing the plugin's apparent security.

The vulnerability history is equally clean, with zero recorded CVEs of any severity. This, combined with the static analysis results, suggests a mature and well-developed plugin that prioritizes security best practices. The absence of any recorded vulnerabilities over time further strengthens this assessment.

In conclusion, based on the provided data, "require-post-category" v2.1 appears to be an exceptionally secure plugin. Its strengths lie in its minimal attack surface, robust code practices, and a clean vulnerability history. There are no apparent weaknesses or specific risks identified in this analysis that would warrant deductions.

Vulnerabilities
None known

Require Post Category Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Require Post Category Release Timeline

v2.1Current
v2.0.3
v2.0.2
v2.0.1
v2.0
v1.1
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0
Code Analysis
Analyzed Mar 16, 2026

Require Post Category Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0
Attack Surface

Require Post Category Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionplugins_loadedrequire-post-category.php:29
actionadmin_enqueue_scriptsrequire-post-category.php:30
Maintenance & Trust

Require Post Category Maintenance & Trust

Maintenance Signals

WordPress version tested6.5.8
Last updatedApr 5, 2024
PHP min version
Downloads27K

Community Trust

Rating98/100
Number of ratings11
Active installs1K
Developer Profile

Require Post Category Developer Profile

Josh Hartman

3 plugins · 2K total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Require Post Category

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/require-post-category/require-post-category-gutenberg.js/wp-content/plugins/require-post-category/require-post-category.js
Script Paths
/wp-content/plugins/require-post-category/require-post-category-gutenberg.js/wp-content/plugins/require-post-category/require-post-category.js

HTML / DOM Fingerprints

JS Globals
require_post_category
FAQ

Frequently Asked Questions about Require Post Category