I Make Plugins Security & Risk Analysis

wordpress.org/plugins/i-make-plugins

For plugin authors. Showcase your plugins on your WordPress site. You only update your readme.txt files!

10 active installs v1.2.3 PHP + WP 3.3+ Updated Oct 11, 2014
directorylistplugin-directory
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is I Make Plugins Safe to Use in 2026?

Generally Safe

Score 85/100

I Make Plugins has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11yr ago
Risk Assessment

The i-make-plugins v1.2.3 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of any identified dangerous functions, raw SQL queries, or file operations is highly commendable. The plugin also demonstrates good practices by consistently using prepared statements for SQL queries and having a nonce check in place. However, there are some areas that warrant attention. Notably, the plugin lacks capability checks, meaning that access to its functionalities is not explicitly restricted by user roles, which could be a concern depending on the nature of the shortcode's functionality. Additionally, while the majority of output is escaped, there is a portion that is not, potentially opening avenues for cross-site scripting (XSS) vulnerabilities if the unescaped output handles user-supplied data. The external HTTP request is also a potential risk vector if not handled securely. The vulnerability history is entirely clean, which is an excellent sign, suggesting a well-maintained and secure codebase over time. Overall, the plugin is well-built with good fundamental security practices, but the lack of capability checks and imperfect output escaping represent minor but addressable risks.

Key Concerns

  • Missing capability checks
  • Unescaped output identified
  • External HTTP request identified
Vulnerabilities
None known

I Make Plugins Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

I Make Plugins Code Analysis

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

Output Escaping

67% escaped3 total outputs
Attack Surface

I Make Plugins Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[implist_template] i-make-plugins.php:75
WordPress Hooks 7
actionadmin_initi-make-plugins.php:46
actionadmin_menui-make-plugins.php:47
filterthe_contenti-make-plugins.php:48
filterthe_contenti-make-plugins.php:49
filteriniti-make-plugins.php:50
actiondo_meta_boxesi-make-plugins.php:51
actionsave_posti-make-plugins.php:52
Maintenance & Trust

I Make Plugins Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedOct 11, 2014
PHP min version
Downloads5K

Community Trust

Rating76/100
Number of ratings6
Active installs10
Developer Profile

I Make Plugins Developer Profile

Mark Jaquith

29 plugins · 176K total installs

69
trust score
Avg Security Score
86/100
Avg Patch Time
3337 days
View full developer profile
Detection Fingerprints

How We Detect I Make Plugins

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
cws-imp-plugin-listcws-imp-plugincws-imp-plugin-titlecws-imp-plugin-description
Shortcode Output
[implist_template][implist][implist_name][implist_url]
FAQ

Frequently Asked Questions about I Make Plugins