Marwan Hatem

<p>SPM by Marwan is a professional-grade diagnostics and intelligence platform designed for WordPress administrators and developers. It provides deep visibility into your WordPress ecosystem, offering real-time monitoring, security auditing, and performance profiling to ensure your site remains fast, secure, and stable.</p>
<h3>The Problem</h3>
<p>Managing a modern WordPress ecosystem is inherently complex. Site owners and developers frequently struggle with:</p>
<ul>
<li><strong>Slow Extensions:</strong> Identifying which specific extension is degrading page load times or consuming excessive server resources.</li>
<li><strong>Hidden PHP Errors:</strong> Unseen warnings and fatal errors that silently break functionality or create vulnerabilities.</li>
<li><strong>Security Risks:</strong> Unmaintained, abandoned, or vulnerable code exposing the site to potential exploits.</li>
<li><strong>Trust Issues:</strong> Uncertainty regarding an extension’s origin, development standards, and code quality.</li>
<li><strong>Update Degradation:</strong> Performance regressions and unexpected conflicts introduced immediately after updates.</li>
</ul>
<h3>Core Features</h3>
<ul>
<li><strong>Real-Time Monitoring Engine:</strong> Actively tracks resource consumption, database queries, and execution times for every active extension. Identifies performance bottlenecks as they happen, preventing systemic slowdowns.</li>
<li><strong>Performance Diagnostics:</strong> Deep-dive profiling for individual extensions. Analyzes memory footprint and script execution to provide actionable intelligence on resource utilization.</li>
<li><strong>Security & Integrity Scanner:</strong> Proactively audits installed extensions against known vulnerability databases, flags high-risk code patterns, and verifies WordPress core files against official checksums to detect malicious tampering.</li>
<li><strong>Japanese SEO Spam Auto-Fix Engine:</strong> A specialized, deep-scanning engine designed to detect and eradicate the notorious “Japanese Keyword Hack”. Features a one-click Auto-Fix that intelligently restores or quarantines hijacked posts to protect your Google ranking without destroying your original content.</li>
</ul>
<h3>Advanced Security: Defeating the Japanese SEO Keyword Hack</h3>
<p>The “Japanese Keyword Hack” is a devastating black-hat SEO attack where hackers exploit vulnerabilities in outdated plugins to inject massive amounts of auto-generated Japanese text and malicious links into your database and core files. This causes Google to flag your site as “hacked,” instantly destroying your SEO ranking.</p>
<p>SPM by Marwan includes a highly specialized engine specifically built to defeat this attack:</p>
<ul>
<li><strong>Deep Database Scanning:</strong> Actively crawls your <code>wp_posts</code> and <code>wp_options</code> tables, utilizing advanced Unicode block detection to find injected Japanese Hiragana, Katakana, and Kanji spam hidden within your legitimate content.</li>
<li><strong>Intelligent Auto-Fix (No Data Loss):</strong> When you click “Auto-Fix”, the scanner doesn’t just blindly delete your hijacked posts. Instead, it scans the WordPress Revision History for each infected post. It finds the last “clean” version of your post (before the hacker touched it) and seamlessly restores it.</li>
<li><strong>Fail-Safe Quarantining:</strong> If a post was created entirely by the hacker (meaning no clean revision exists), or if you have revisions disabled, the engine will safely quarantine the post by setting its status to <strong>Draft</strong>. This instantly removes the spam from the public internet—stopping the SEO bleed—while preserving the draft in your admin panel so you don’t lose any data.</li>
<li><strong>Orphaned File Detection:</strong> Scans your entire server structure to locate and quarantine backdoor PHP scripts that hackers leave behind to reinfect your site after you clean it.</li>
<li><strong>Core Checksum Verification:</strong> Verifies every single WordPress core file against the official WordPress.org cryptographic checksums to detect hidden cloaking scripts.</li>
<li><strong>Trust Verification:</strong> Evaluates code based on developer reputation, update frequency, repository standing, and code integrity. Establishes a trust score to help you make informed decisions about your technology stack.</li>
<li><strong>Historical Analytics:</strong> Maintains a robust ledger of performance and security metrics over time. Visualizes trends to help you understand the long-term impact of specific extensions and updates.</li>
<li><strong>Action Layer (Scan / Safe Mode / Reporting):</strong> Provides immediate remediation tools. Execute targeted scans, isolate problematic extensions using Safe Mode, and generate comprehensive diagnostics reports.</li>
</ul>
<h3>External Services</h3>
<p>This plugin utilizes the WordPress.org Plugins API (https://api.wordpress.org) to verify plugin licenses and retrieve information about installed plugins.<br />
* <strong>What data is sent:</strong> The names and slugs of your active plugins are sent in the API request.<br />
* <strong>When it is sent:</strong> Data is sent when the plugin performs a scheduled background scan or when you manually click “Deep Scan” or “Refresh Now” on the dashboard.<br />
* <strong>Why it is used:</strong> To verify that the plugins running on your site are authentic, properly licensed, and available on the official WordPress.org directory, which enhances your site’s security and trust metrics.</p>
<p>For more information, please refer to the <a href="https://wordpress.org/about/privacy/" rel="ugc">WordPress.org Privacy Policy</a>.</p>


SPM by Marwan

Tracks load time and PHP errors for each active extension, storing logs in a custom database table.

Viktor Szépe

<h4>Only for development!</h4>
<h4>Now with OPcache memory consumption support</h4>
<p>This plugin dumps the colorized filenames and memory consumptions or file sizes after the normal WordPress HTML output, after the closing html tag. This generates invalid HTML but gives you an overview of loaded plugins and the current theme.</p>
<p><em>What’s running</em> lists all files parsed and executed by the PHP engine. It can be used for plugin or theme refactoring.</p>
<h4>Now you can highlight your own plugin and theme</h4>
<p>Provide a part of its path in wp-config.php:</p>
<pre><code>define( 'WHATS_RUNNING_HIGHLIGHT', 'wp-content/plugins/my-plugin' ); </code></pre>
<h4>Color codes</h4>
<ul>
<li>your code is highlighted with YELLOW background</li>
<li>plugin files are in BLUE</li>
<li>themes files are in ORANGE</li>
<li>files in the wp-includes directory are in GREEN</li>
<li>files in the wp-admin directory are in GREY</li>
<li>all other files are in RED</li>
<li>VIOLET bar after the filename represents the file size ( 0.5 kB/px )</li>
<li>DARK MAGENTA bar after the filename represents the OPcache memory consumption ( 1 kB/px )</li>
</ul>
<h4>Links</h4>
<p>You can watch <a href="https://core.trac.wordpress.org/ticket/28364" rel="nofollow ugc">WP core bug #28364</a> to get more information about <a href="https://github.com/szepeviktor/WPHW/blob/master/wp-entry-points.md" rel="nofollow ugc">WordPress entry points</a>.</p>
<p>You can find some documentaion here what makes a WordPress plugin efficient: https://github.com/szepeviktor/WPHW</p>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/whats-running" rel="nofollow ugc">GitHub</a>.</p>


What's running

Lists WordPress require() calls mainly for plugin code refactoring.

SPM by Marwan vs What's running