Gosign – Vimeo Video Player Block Security & Risk Analysis

wordpress.org/plugins/gosign-vimeo-video-player-block

Add Vimeo Video Player Block with custom splash image and also can set options for vimeo video player like autoplay, loop and many more.

60 active installs v2.0.5 PHP + WP 5.8+ Updated Oct 7, 2021
gutenberg-vimeo-video-player-blockvimeo-player-block-with-splash-imagevimeo-video-playervimeo-video-player-with-optionswordpress-vimeo-video-player
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Gosign – Vimeo Video Player Block Safe to Use in 2026?

Generally Safe

Score 85/100

Gosign – Vimeo Video Player Block has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 4yr ago
Risk Assessment

The static analysis of gosign-vimeo-video-player-block v2.0.5 reveals a remarkably secure codebase with no identified entry points, dangerous functions, or unescaped outputs. The complete absence of SQL queries that don't use prepared statements, file operations, external HTTP requests, and taint flows with unsanitized paths strongly suggests adherence to secure coding practices. The plugin also demonstrates robust security by implementing capability checks, indicating that actions performed by the plugin are properly authorized.

The vulnerability history is equally positive, with no recorded CVEs of any severity. This lack of past vulnerabilities, combined with the current clean static analysis, points to a well-maintained and secure plugin. The absence of bundled libraries also removes a common attack vector associated with outdated or vulnerable third-party code. Overall, the plugin presents an excellent security posture with no apparent weaknesses based on the provided data.

Vulnerabilities
None known

Gosign – Vimeo Video Player Block Security Vulnerabilities

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

Gosign – Vimeo Video Player 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

Gosign – Vimeo Video Player Block Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionadmin_initgosign-vimeo-video-player-block.php:110
actioninitgosign-vimeo-video-player-block.php:115
actionenqueue_block_editor_assetsgosign-vimeo-video-player-block.php:118
actionwp_enqueue_scriptsgosign-vimeo-video-player-block.php:119
actionplugins_loadedgosign-vimeo-video-player-block.php:189
Maintenance & Trust

Gosign – Vimeo Video Player Block Maintenance & Trust

Maintenance Signals

WordPress version tested5.8.13
Last updatedOct 7, 2021
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs60
Alternatives

Gosign – Vimeo Video Player Block Alternatives

No alternatives data available yet.

Developer Profile

Gosign – Vimeo Video Player Block Developer Profile

Gosign

19 plugins · 5K total installs

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

How We Detect Gosign – Vimeo Video Player Block

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/gosign-vimeo-video-player-block/blocks/index.min.js/wp-content/plugins/gosign-vimeo-video-player-block/blocks/style.min.css
Script Paths
/wp-content/plugins/gosign-vimeo-video-player-block/blocks/index.min.js

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Gosign – Vimeo Video Player Block