Terminal Block Security & Risk Analysis

wordpress.org/plugins/terminal-block

Display rich text in a terminal window.

100 active installs v0.1.3.3 PHP 7.0+ WP 5.9+ Updated Oct 22, 2024
blockblockscodegutenbergterminal
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Terminal Block Safe to Use in 2026?

Generally Safe

Score 92/100

Terminal Block has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The "terminal-block" plugin v0.1.3.3 exhibits a strong security posture based on the provided static analysis. The plugin has no identified attack surface through AJAX handlers, REST API routes, shortcodes, or cron events, which significantly reduces the potential for unauthorized access or manipulation. Furthermore, the code analysis reveals no dangerous functions, all SQL queries are properly prepared, and all output is correctly escaped, indicating good development practices for preventing common vulnerabilities like SQL injection and cross-site scripting.

The absence of any taint analysis findings, file operations, external HTTP requests, and missing nonce or capability checks also points to a secure implementation. The plugin's vulnerability history is completely clear, with no recorded CVEs of any severity. This suggests a diligent approach to security and a lack of previously discovered flaws.

Overall, the plugin appears to be very secure, with no exploitable weaknesses identified in the static analysis or its historical vulnerability data. The development team has implemented robust security measures, resulting in a low-risk profile.

Vulnerabilities
None known

Terminal Block Security Vulnerabilities

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

Terminal Block Release Timeline

v0.1.3.3Current
v0.1.3.2
v0.1.3.1
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Code Analysis
Analyzed Mar 16, 2026

Terminal Block 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

Terminal Block Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actioninitterminal-block.php:20
actionwp_enqueue_scriptsterminal-block.php:31
Maintenance & Trust

Terminal Block Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedOct 22, 2024
PHP min version7.0
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs100
Developer Profile

Terminal Block Developer Profile

Suzen Fylke

1 plugin · 100 total installs

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

How We Detect Terminal Block

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/terminal-block/build
Script Paths
/wp-content/plugins/terminal-block/assets/scripts/terminal.js

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Terminal Block