Github Contributors Security & Risk Analysis

wordpress.org/plugins/github-contributors

Provides a simple short code for displaying a list of contributors from any Github repository.

10 active installs v1.0.1 PHP + WP 3.2+ Updated Aug 20, 2012
contributorsgithubmordaukpippin-williamsonpippinsplugins
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Github Contributors Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The github-contributors plugin, in version 1.0.1, exhibits a generally strong security posture based on the provided static analysis. The absence of dangerous functions, the exclusive use of prepared statements for SQL queries, and 100% proper output escaping are all commendable security practices. Furthermore, the plugin has no recorded vulnerabilities (CVEs) and no indications of critical or high-severity taint flows, suggesting a low risk of exploitation through common attack vectors like SQL injection or cross-site scripting. The limited attack surface, consisting of a single shortcode with no reported unauthenticated entry points, further contributes to its secure design.

However, there are areas that warrant attention. The most significant concern is the complete lack of nonce checks and capability checks. This means that any functionality exposed through the shortcode, or any potential future additions, could be invoked by any authenticated user without proper authorization or verification, potentially leading to privilege escalation or unintended actions. Additionally, while the external HTTP request is not inherently a vulnerability, it represents a potential attack vector if the target service is compromised or if sensitive data is transmitted insecurely. The absence of taint analysis flows, while positive in this instance, could also be due to the limited scope of the analysis or the simple nature of the code; it does not guarantee the absence of such issues in more complex scenarios.

In conclusion, the github-contributors plugin has a strong foundation of secure coding practices, particularly concerning data handling and SQL operations, and a clean vulnerability history. The primary weakness lies in the lack of authorization and verification mechanisms for its entry points. Addressing the missing nonce and capability checks would significantly bolster its security. The presence of an external HTTP request, while not a direct vulnerability, should be monitored for potential risks.

Key Concerns

  • Missing nonce checks
  • Missing capability checks
  • External HTTP request without clear context
Vulnerabilities
None known

Github Contributors Security Vulnerabilities

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

Github Contributors Code Analysis

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

Output Escaping

100% escaped5 total outputs
Attack Surface

Github Contributors Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[github_contributors] github-contributors.php:50
Maintenance & Trust

Github Contributors Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedAug 20, 2012
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Github Contributors Developer Profile

Pippin Williamson

19 plugins · 920 total installs

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

How We Detect Github Contributors

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
pw_github_contributorspw_gh_pw_gh_contributorpw_gh_name
Data Attributes
id="pw_github_contributors"
Shortcode Output
<div id="pw_github_contributors" class="pw_gh_<div class="pw_gh_contributor"<img src="<p class="pw_gh_name">
FAQ

Frequently Asked Questions about Github Contributors