[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqOEqIaarKObew_wP2g10H7ryS6Id5gC_UT_ecVg2PI0":3,"$faT_V1C34drxsUwODH0bo9lHjob2_FQuAwPYziRpfiCk":253,"$fWIOOKgQw_z3iFxTTcgywQlrGjheyJL_t6OG9J6dlIzQ":257},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":13,"vuln_count":11,"unpatched_count":11,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":35,"analysis":125,"fingerprints":210},"taiji-template-inspector","Taiji Template Inspector","1.0.0","jack89ita","https:\u002F\u002Fprofiles.wordpress.org\u002Fjack89ita\u002F","\u003Cp>When you modify a WordPress template, you might be affecting dozens of pages without even knowing it. \u003Cstrong>Taiji Template Inspector\u003C\u002Fstrong> gives you full visibility: instantly see which pages, posts and custom post types use each template — before you change a single line of code.\u003C\u002Fp>\n\u003Cp>Designed for WordPress developers and agencies working on complex sites, it turns template management from a guessing game into a controlled, auditable process.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FJack89ita\u002Ftaiji-template-inspector\" rel=\"nofollow ugc\">View on GitHub\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>What you can do\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>See every page affected by any template\u003C\u002Fstrong> — at a glance, sorted by usage count so the most impactful templates are always first\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Expand any template row\u003C\u002Fstrong> to inspect the individual posts and pages assigned to it\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Open all impacted pages in one click\u003C\u002Fstrong> — choose between frontend preview or backend editor\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Spot orphaned templates\u003C\u002Fstrong> — files missing from the theme are automatically flagged, so you can clean up safely\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Export a full usage report as CSV\u003C\u002Fstrong> for QA workflows and documentation\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Filter by language\u003C\u002Fstrong> when using WPML or Polylang on multilingual sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Search templates instantly\u003C\u002Fstrong> with the live search bar\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Built for real projects\u003C\u002Fh4>\n\u003Cp>Taiji Template Inspector is read-only and completely safe to use in production. It uses optimised database queries with WordPress transient caching to minimise performance impact, even on large sites with hundreds of pages and multiple custom post types.\u003C\u002Fp>\n\u003Cp>No settings to configure. Install, activate, and find it under \u003Cstrong>Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Taiji Template Inspector\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch4>Who is this for?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Developers\u003C\u002Fstrong> maintaining or refactoring WordPress themes\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agencies\u003C\u002Fstrong> managing client sites with complex template structures\u003C\u002Fli>\n\u003Cli>\u003Cstrong>QA teams\u003C\u002Fstrong> who need to verify which pages are affected before deploying changes\u003C\u002Fli>\n\u003C\u002Ful>\n","Instantly see which pages a template powers, so every change is intentional — never accidental.",0,335,100,1,"2026-03-24T10:01:00.000Z","6.9.5","5.8","7.4",[20,21,22,23,24],"debugging","developer-tools","qa","template-management","templates","https:\u002F\u002Fgithub.com\u002FJack89ita\u002Ftaiji-template-inspector","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftaiji-template-inspector.zip",null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":11,"avg_security_score":13,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},30,94,"2026-08-29T13:44:59.014Z",[36,59,76,93,109],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":17,"requires_php":50,"tags":51,"homepage":55,"download_link":56,"security_score":57,"vuln_count":14,"unpatched_count":11,"last_vuln_date":58,"fetched_at":28},"debug-log-viewer","Debug Log Viewer","2.4","Oleksandr Lysyi","https:\u002F\u002Fprofiles.wordpress.org\u002Flysyiweb\u002F","\u003Ch4>Debug Log Viewer: Your Essential WordPress Debugging Tool\u003C\u002Fh4>\n\u003Cp>Tired of struggling to access and understand your WordPress debug.log\u003Cbr \u002F>\nfile?\u003C\u002Fp>\n\u003Cp>Debug Log Viewer simplifies WordPress debugging by providing a\u003Cbr \u002F>\nuser-friendly interface to view, search, and manage your debug.log\u003Cbr \u002F>\ndirectly within your WordPress admin area.\u003C\u002Fp>\n\u003Cp>It is designed for WordPress developers, site administrators,\u003Cbr \u002F>\nfreelancers, and anyone who needs to quickly identify and resolve\u003Cbr \u002F>\nwebsite issues.\u003C\u002Fp>\n\u003Cp>Debug Log Viewer helps you find errors faster without using FTP, hosting\u003Cbr \u002F>\npanels, or manually opening log files.\u003C\u002Fp>\n\u003Ch4>Gain Real-Time Insights into Your WordPress Site Health\u003C\u002Fh4>\n\u003Cp>Monitor errors, warnings, and deprecated function notices in real-time.\u003Cbr \u002F>\nDebug Log Viewer helps you identify problems early and maintain a more\u003Cbr \u002F>\nstable WordPress environment.\u003C\u002Fp>\n\u003Ch4>Key Features for Efficient WordPress Debugging\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Real-Time Log Viewer: Monitor your WordPress debug.log file in\u003Cbr \u002F>\nreal-time, directly from your WordPress dashboard. No more hunting\u003Cbr \u002F>\nfor files via FTP or cPanel!\u003C\u002Fli>\n\u003Cli>Easy Debug Log Access: Access and view your full debug log within a\u003Cbr \u002F>\nclean and intuitive interface.\u003C\u002Fli>\n\u003Cli>Search and Filtering: Quickly find specific log entries with\u003Cbr \u002F>\npowerful search and filtering options. Filter by error type,\u003Cbr \u002F>\nkeywords, and date range (Pro).\u003C\u002Fli>\n\u003Cli>Pagination: Navigate through large debug logs with ease using\u003Cbr \u002F>\npagination, ensuring smooth performance even with extensive logs.\u003C\u002Fli>\n\u003Cli>Email Alerts for Errors: Get email alerts when new errors are\u003Cbr \u002F>\nlogged. Pro users can customize error severity levels and\u003Cbr \u002F>\nrecipients.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Flexible Settings Panel\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Control WP_DEBUG Constants: Enable or disable WP_DEBUG and\u003Cbr \u002F>\nWP_DEBUG_LOG constants directly from the plugin settings.\u003C\u002Fli>\n\u003Cli>Customize Logging Options: Configure your debug log settings to\u003Cbr \u002F>\nmatch your needs.\u003C\u002Fli>\n\u003Cli>Custom Log Path Support: Automatically detect and read custom\u003Cbr \u002F>\ndebug.log locations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Benefits of Using Debug Log Viewer\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Save Time and Effort: Stop manually accessing and parsing your debug\u003Cbr \u002F>\nlog file.\u003C\u002Fli>\n\u003Cli>Faster Error Detection: Monitor errors as they happen and reduce\u003Cbr \u002F>\ntroubleshooting time.\u003C\u002Fli>\n\u003Cli>Simplified Troubleshooting: Quickly identify the source of errors\u003Cbr \u002F>\nand warnings.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Log Viewer Pro Features\u003C\u002Fh4>\n\u003Cp>Upgrade to Pro and get advanced tools for professional WordPress\u003Cbr \u002F>\ndebugging and site maintenance:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Advanced Email Alerts: Choose error levels and send notifications to\u003Cbr \u002F>\nmultiple recipients.\u003C\u002Fli>\n\u003Cli>CSV Export: Export debug log entries for analysis, reporting, or\u003Cbr \u002F>\nsharing.\u003C\u002Fli>\n\u003Cli>Custom Date Range Filtering: Analyze logs from specific time\u003Cbr \u002F>\nperiods.\u003C\u002Fli>\n\u003Cli>Infinite Scroll Log Viewer: Browse large log files smoothly without\u003Cbr \u002F>\npagination interruptions.\u003C\u002Fli>\n\u003Cli>Advanced Log Cleanup Controls: Manage debug.log size with custom\u003Cbr \u002F>\nlimits, schedules, cleanup methods, and retention settings.\u003C\u002Fli>\n\u003Cli>Cleanup History: Review previous cleanup actions and track log\u003Cbr \u002F>\nmaintenance.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why choose Debug Log Viewer Pro?\u003C\u002Fh4>\n\u003Cp>Managing WordPress errors is not only about viewing logs.\u003C\u002Fp>\n\u003Cp>Large debug files can consume disk space, become difficult to analyze,\u003Cbr \u002F>\nand slow down troubleshooting.\u003C\u002Fp>\n\u003Cp>Pro gives you automation tools to monitor, export, filter, and maintain\u003Cbr \u002F>\nyour debug logs efficiently.\u003C\u002Fp>\n\u003Ch4>Who is Debug Log Viewer For?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress developers\u003C\u002Fli>\n\u003Cli>Website administrators\u003C\u002Fli>\n\u003Cli>Freelancers managing client sites\u003C\u002Fli>\n\u003Cli>Agencies maintaining WordPress websites\u003C\u002Fli>\n\u003Cli>Anyone who wants an easy way to monitor WordPress errors\u003C\u002Fli>\n\u003C\u002Ful>\n","Effortlessly view, search, filter and manage your WordPress debug.log in the admin dashboard. Real-time monitoring and email alerts",1000,16436,80,3,"2026-06-25T05:59:00.000Z","7.0.2","7.2",[52,53,20,21,54],"debug","debug-log","error-log","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-viewer.2.4.zip",99,"2025-10-29 00:00:00",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":11,"num_ratings":11,"last_updated":69,"tested_up_to":49,"requires_at_least":70,"requires_php":18,"tags":71,"homepage":55,"download_link":75,"security_score":13,"vuln_count":11,"unpatched_count":11,"last_vuln_date":27,"fetched_at":28},"postmeta-viewer","PostMeta Viewer – Custom Fields Inspector","1.1","wpwebguru","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpwebguru\u002F","\u003Cp>\u003Cstrong>PostMeta Viewer\u003C\u002Fstrong> is an essential utility for WordPress developers who work with custom fields and post meta. Whether you’re using Advanced Custom Fields (ACF), Pods, Toolset, or custom-coded meta fields, this plugin provides a clean and developer-friendly interface to explore, search, and analyze meta data across your entire WordPress site.\u003C\u002Fp>\n\u003Cp>It is designed strictly as a \u003Cstrong>read-only inspection tool\u003C\u002Fstrong>, making it safe for production environments.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Complete Meta Overview\u003C\u002Fstrong>\u003Cbr \u002F>\nBrowse all posts, pages, and custom post types with total custom field counts.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Detailed Meta Inspection\u003C\u002Fstrong>\u003Cbr \u002F>\nView all meta keys and values for any individual post, taxonomy term, user, or comment.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Powerful Search & Filtering\u003C\u002Fstrong>\u003Cbr \u002F>\n– Search across post titles, content, meta keys, and meta values\u003Cbr \u002F>\n– Filter by post type, post status, and date range\u003Cbr \u002F>\n– Filter by specific meta key existence\u003Cbr \u002F>\n– Filter by meta value type (string, array, JSON, numeric, empty)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Meta Inspector Everywhere\u003C\u002Fstrong>\u003Cbr \u002F>\n– Post edit screen meta box (configurable per post type)\u003Cbr \u002F>\n– Taxonomy term edit screens (categories, tags, custom taxonomies)\u003Cbr \u002F>\n– User profile edit screens\u003Cbr \u002F>\n– Comment edit screen\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Developer-Friendly Data Display\u003C\u002Fstrong>\u003Cbr \u002F>\n– Proper formatting for serialized, array, and JSON meta values\u003Cbr \u002F>\n– One‑click “beautify” toggle to expand complex data structures\u003Cbr \u002F>\n– Dark‑style pre‑formatted output for readability\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Post Statistics\u003C\u002Fstrong>\u003Cbr \u002F>\nQuick insights into total posts and filtered results.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Extensive Settings Page\u003C\u002Fstrong>\u003Cbr \u002F>\n– Choose which roles can access the inspector\u003Cbr \u002F>\n– Toggle visibility on post types, taxonomies, users, and comments\u003Cbr \u002F>\n– Hide internal meta keys (those starting with an underscore)\u003Cbr \u002F>\n– Adjust items per page\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Responsive Admin UI\u003C\u002Fstrong>\u003Cbr \u002F>\nWorks smoothly across all screen sizes.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Ideal For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>ACF Developers\u003C\u002Fstrong> – Debug and verify stored ACF field data  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin Developers\u003C\u002Fstrong> – Inspect custom meta added by plugins  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Theme Developers\u003C\u002Fstrong> – Validate custom field implementations  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site Debugging\u003C\u002Fstrong> – Identify and resolve metadata issues  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Migration Projects\u003C\u002Fstrong> – Analyze existing meta structures  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Learning WordPress\u003C\u002Fstrong> – Understand how post meta works internally\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Ch4>Getting Started\u003C\u002Fh4>\n\u003Col>\n\u003Cli>After activation, go to \u003Cstrong>PostMeta Viewer\u003C\u002Fstrong> (top-level menu)\u003C\u002Fli>\n\u003Cli>View a list of all posts along with their custom field counts\u003C\u002Fli>\n\u003Cli>Use search and filter options to narrow results\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>View Details\u003C\u002Fstrong> to inspect meta for a specific post\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Using Search & Filters\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>Search Box\u003C\u002Fstrong> – Search across post titles, content, meta keys, and values  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post Type Filter\u003C\u002Fstrong> – Filter posts, pages, or custom post types  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Meta Key Filter\u003C\u002Fstrong> – Filter by existing meta keys  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Date Range\u003C\u002Fstrong> – Filter posts by creation date  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post Status\u003C\u002Fstrong> – Published, draft, pending, etc.  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Value Type Filter\u003C\u002Fstrong> – String, array, JSON, numeric, or empty  \u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Apply Filters\u003C\u002Fstrong> to update results\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Viewing Meta Details\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Click \u003Cstrong>View Details\u003C\u002Fstrong> from the main list\u003C\u002Fli>\n\u003Cli>View a table of all meta keys and values\u003C\u002Fli>\n\u003Cli>Serialized and complex data is displayed in a readable, beautified format\u003C\u002Fli>\n\u003Cli>Use \u003Cstrong>Back to List\u003C\u002Fstrong> to return\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Inspecting Meta on Other Screens\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>Post Edit Screen\u003C\u002Fstrong> – The \u003Cstrong>Custom Fields Inspector\u003C\u002Fstrong> meta box appears below the content editor (for enabled post types)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Taxonomy Term Edit Screen\u003C\u002Fstrong> – A similar box appears on category, tag, and custom taxonomy edit pages\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User Profile Edit Screen\u003C\u002Fstrong> – The inspector is shown on user profile pages\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comment Edit Screen\u003C\u002Fstrong> – The inspector is shown on the single comment edit page\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>All boxes respect the role and visibility settings.\u003C\u002Fp>\n\u003Ch4>Configuring the Plugin\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>PostMeta Viewer \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Adjust:\n\u003Cul>\n\u003Cli>\u003Cstrong>Items Per Page\u003C\u002Fstrong> – number of posts shown in the main list\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Access Roles\u003C\u002Fstrong> – checkboxes for every registered user role; only checked roles can view post, term, user, and comment meta data (Administrator is always enabled and cannot be unchecked, to prevent accidental lockout)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hide Internal Keys\u003C\u002Fstrong> – toggle visibility of meta keys starting with \u003Ccode>_\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enabled Post Types\u003C\u002Fstrong> – checkboxes for every public post type, controlling which post-type edit screens show the Custom Fields Inspector meta box\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Inspector Locations\u003C\u002Fstrong> – enable\u002Fdisable meta boxes on taxonomies, users, and comments\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Save your changes\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPL v2 or later.\u003C\u002Fp>\n\u003Cp>This program is free software; you can redistribute it and\u002For modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version.\u003C\u002Fp>\n\u003Cp>This program is distributed without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose.\u003C\u002Fp>\n","A powerful debugging tool for WordPress developers to inspect and analyze post meta (custom fields) across posts, pages, custom post types, taxonomy t …",70,1186,"2026-06-21T07:45:00.000Z","5.6",[72,73,20,21,74],"acf","custom-fields","post-meta","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpostmeta-viewer.1.1.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":13,"num_ratings":14,"last_updated":86,"tested_up_to":16,"requires_at_least":87,"requires_php":18,"tags":88,"homepage":55,"download_link":92,"security_score":13,"vuln_count":11,"unpatched_count":11,"last_vuln_date":27,"fetched_at":28},"mcp-tracker","MCP Tracker","1.0.1","WPVibes","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpvibes\u002F","\u003Cp>MCP Tracker is an admin-only WordPress plugin designed to monitor and log MCP (Model Context Protocol) requests made to the Abilities API on your WordPress site.\u003Cbr \u002F>\nIf you are using the Abilities API to power AI-driven tools or MCP-based integrations, MCP Tracker gives you complete visibility into how those tools interact with your REST endpoints — without modifying or interfering with request flow.\u003Cbr \u002F>\nThe plugin automatically detects MCP requests (identified via the \u003Ccode>Mcp-Session-Id\u003C\u002Fcode> header), records detailed request and response data, and presents everything in a structured, filterable interface inside WordPress Admin.\u003Cbr \u002F>\nWhether you’re debugging Abilities API integrations, auditing MCP tool usage, or analyzing response behavior, MCP Tracker provides the observability layer you need.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automatic MCP Detection\u003C\u002Fstrong>\u003Cbr \u002F>\nIdentifies MCP requests related to Abilities API using the \u003Ccode>Mcp-Session-Id\u003C\u002Fcode> header.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comprehensive Logging\u003C\u002Fstrong>\u003Cbr \u002F>\nLogs route, method, headers, request payload, response status, and response body.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User Attribution\u003C\u002Fstrong>\u003Cbr \u002F>\nDisplays which WordPress user (or guest) initiated the MCP request.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Advanced Filtering\u003C\u002Fstrong>\u003Cbr \u002F>\nFilter logs by date range, tool name, and user for targeted analysis.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Formatted JSON Inspection\u003C\u002Fstrong>\u003Cbr \u002F>\nView complete request and response data in a structured format.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Privacy Focused\u003C\u002Fstrong>\u003Cbr \u002F>\nAll logs remain stored in your WordPress database. No external transmission or telemetry.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Performance Optimized\u003C\u002Fstrong>\u003Cbr \u002F>\nEfficient logging using native WordPress REST hooks and optimized queries.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Use Cases\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Debug Abilities API integrations  \u003C\u002Fli>\n\u003Cli>Monitor MCP-based AI tool usage  \u003C\u002Fli>\n\u003Cli>Analyze REST response patterns  \u003C\u002Fli>\n\u003Cli>Audit MCP activity on production sites  \u003C\u002Fli>\n\u003Cli>Investigate failed or unexpected tool executions  \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Technical Details\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Uses WordPress REST API hooks for non-intrusive logging  \u003C\u002Fli>\n\u003Cli>Custom indexed database table for efficient storage  \u003C\u002Fli>\n\u003Cli>Admin-only access with capability checks  \u003C\u002Fli>\n\u003Cli>Nonce verification for secure actions  \u003C\u002Fli>\n\u003Cli>Prepared SQL statements for database safety  \u003C\u002Fli>\n\u003Cli>Self-healing table creation on activation\u003C\u002Fli>\n\u003C\u002Ful>\n","Records and displays MCP-related REST API requests made to your WordPress site.",20,561,"2026-04-27T11:05:00.000Z","6.9",[20,21,89,90,91],"logging","mcp","rest-api","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmcp-tracker.1.0.1.zip",{"slug":94,"name":95,"version":96,"author":97,"author_profile":98,"description":99,"short_description":100,"active_installs":101,"downloaded":102,"rating":11,"num_ratings":11,"last_updated":103,"tested_up_to":104,"requires_at_least":17,"requires_php":18,"tags":105,"homepage":107,"download_link":108,"security_score":13,"vuln_count":11,"unpatched_count":11,"last_vuln_date":27,"fetched_at":28},"log-iq","LogIQ – Intelligent Debug Log Viewer","1.2.0","akmelias","https:\u002F\u002Fprofiles.wordpress.org\u002Fakmelias\u002F","\u003Cp>\u003Cstrong>Debugging WordPress shouldn’t be painful.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Most developers deal with debug logs the hard way: SSH into the server, \u003Ccode>tail -f debug.log\u003C\u002Fcode>, squint at wall-of-text output, scroll endlessly to find the one error that matters. It’s slow, it’s fragile, and it pulls you out of your flow.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>LogIQ fixes that.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>LogIQ is an intelligent debug log viewer built for WordPress developers. It lives in your admin dashboard, parses your log file automatically, and surfaces exactly what you need — with search, filters, collapsible stack traces, and one-click editor access. No config files. No terminal. No wasted time.\u003C\u002Fp>\n\u003Ch4>What Makes LogIQ Different\u003C\u002Fh4>\n\u003Cp>Most log plugins just dump raw text into a \u003Ccode>\u003Ctextarea>\u003C\u002Fcode>. LogIQ actually understands your logs.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Categorizes every entry by level (Fatal, Error, Warning, Notice, Deprecated, Info, Debug, DB Error)\u003C\u002Fli>\n\u003Cli>Detects duplicate\u002Frepeated errors and groups them with a count badge\u003C\u002Fli>\n\u003Cli>Collapses multi-line stack traces so your screen isn’t buried in noise\u003C\u002Fli>\n\u003Cli>Highlights your search term inline across all matching entries\u003C\u002Fli>\n\u003Cli>Shows relative timestamps (“3 minutes ago”) with the full timestamp on hover\u003C\u002Fli>\n\u003Cli>Lets you copy any entry to clipboard in one click\u003C\u002Fli>\n\u003Cli>Opens the exact file and line in VS Code, PhpStorm, or Sublime Text — no copy-pasting paths\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Core Features\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Smart Log Parsing\u003C\u002Fstrong>\u003Cbr \u002F>\nAutomatically detects PHP Fatal errors, Warnings, Notices, Deprecated calls, Database errors, and custom \u003Ccode>error_log()\u003C\u002Fcode> output. No setup required.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Full-Text Search\u003C\u002Fstrong>\u003Cbr \u002F>\nSearch across message content, file paths, and timestamps instantly. Matches are highlighted in-place with a count of results.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Level Filters\u003C\u002Fstrong>\u003Cbr \u002F>\nFilter by Fatal, Error, Warning, Notice, Deprecated, Info, Debug, or DB Error with a single click. Counts update live with each filter.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Collapsible Stack Traces\u003C\u002Fstrong>\u003Cbr \u002F>\nLong stack traces are collapsed by default. Expand only the ones you care about — keeping your view clean and focused.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Duplicate Detection\u003C\u002Fstrong>\u003Cbr \u002F>\nConsecutive identical log entries are automatically grouped into a single entry with a \u003Ccode>×N\u003C\u002Fcode> badge. Stop scrolling past 200 copies of the same warning.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Relative Timestamps\u003C\u002Fstrong>\u003Cbr \u002F>\nLog timestamps show as “2 minutes ago”, “1 hour ago” etc. Hover to see the full timestamp. Great for spotting when errors started.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Copy to Clipboard\u003C\u002Fstrong>\u003Cbr \u002F>\nOne-click copy on every log entry. Paste directly into Slack, a bug report, or a support ticket.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Log Export\u003C\u002Fstrong>\u003Cbr \u002F>\nDownload your current filtered view as a \u003Ccode>.log\u003C\u002Fcode> file or structured \u003Ccode>.json\u003C\u002Fcode> — perfect for sharing with your team or attaching to issue trackers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Editor Integration\u003C\u002Fstrong>\u003Cbr \u002F>\nClick any file path in a log entry to jump directly to that file and line in:\u003Cbr \u002F>\n* Visual Studio Code\u003Cbr \u002F>\n* PhpStorm\u003Cbr \u002F>\n* Sublime Text\u003Cbr \u002F>\n* Falls back to \u003Ccode>file:\u002F\u002F\u003C\u002Fcode> if no supported editor is detected\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Auto-Refresh\u003C\u002Fstrong>\u003Cbr \u002F>\nThe log viewer refreshes automatically every 30 seconds so you can watch logs update in real time without touching the page.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Secure by Default\u003C\u002Fstrong>\u003Cbr \u002F>\nOnly users with \u003Ccode>manage_options\u003C\u002Fcode> capability can access LogIQ. All AJAX requests are nonce-verified. Sensitive values (passwords, API keys, auth tokens) are masked automatically before display.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Pagination\u003C\u002Fstrong>\u003Cbr \u002F>\nHandles large log files gracefully — reads up to 5 MB from the end of the file, paginates entries, and never loads more than needed.\u003C\u002Fp>\n\u003Ch4>Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress plugin and theme developers\u003C\u002Fli>\n\u003Cli>Agencies managing multiple client sites\u003C\u002Fli>\n\u003Cli>Developers debugging WooCommerce, REST APIs, and third-party integrations\u003C\u002Fli>\n\u003Cli>Anyone who’s tired of \u003Ccode>tail -f debug.log\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How to Use error_log() with LogIQ\u003C\u002Fh4>\n\u003Cp>LogIQ reads from WordPress’s standard debug log. Write to it from anywhere in your code:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>error_log( 'Something happened' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For arrays and objects:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>error_log( print_r( $my_array, true ) );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For exceptions:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>error_log( $exception->getMessage() . ' in ' . $exception->getFile() . ':' . $exception->getLine() );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>LogIQ does not collect, transmit, or store any personal data outside of your own server. All log data remains local. The plugin does not make any external HTTP requests.\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>Developed by \u003Ca href=\"https:\u002F\u002Fakmelias.com\" rel=\"nofollow ugc\">AKM Elias\u003C\u002Fa>. If LogIQ saves you time, consider leaving a review on WordPress.org — it helps more developers find it.\u003C\u002Fp>\n","Stop digging through raw log files. LogIQ gives WordPress developers a smart, searchable, and beautiful debug log viewer — right inside the admin.",10,830,"2026-03-20T05:54:00.000Z","6.8.6",[53,20,21,54,106],"log-viewer","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flog-iq\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flog-iq.1.2.0.zip",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":11,"downloaded":117,"rating":11,"num_ratings":11,"last_updated":118,"tested_up_to":49,"requires_at_least":17,"requires_php":18,"tags":119,"homepage":123,"download_link":124,"security_score":13,"vuln_count":11,"unpatched_count":11,"last_vuln_date":27,"fetched_at":28},"cronpulse","Cron Pulse","1.1.0","Farhan Ali","https:\u002F\u002Fprofiles.wordpress.org\u002Ffarhanalidev\u002F","\u003Cp>WordPress developers fly blind with WP-Cron. The core tools give you no visibility into whether scheduled jobs are actually running, how long they take, or when they last fired.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Cron Pulse\u003C\u002Fstrong> adds a clean dashboard under \u003Cstrong>Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Cron Pulse\u003C\u002Fstrong> that shows everything you need at a glance:\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Scheduled Jobs table\u003C\u002Fstrong> — hook name, recurrence schedule, next run time, last run time, execution duration\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Status indicators\u003C\u002Fstrong> — Healthy \u002F Overdue \u002F Failing \u002F Pending color coding so problems jump out immediately\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Overdue detection\u003C\u002Fstrong> — instantly see jobs that should have fired but haven’t\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Admin bar badge\u003C\u002Fstrong> — a small warning indicator on every wp-admin (and front-end) page when something needs attention, so you don’t have to remember to check the dashboard\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Run Now\u003C\u002Fstrong> — manually trigger any cron hook with one click (great for testing)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Unschedule\u003C\u002Fstrong> — delete a stuck or duplicate scheduled event straight from the dashboard\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sortable columns and pagination\u003C\u002Fstrong> — click Next Run or Duration to sort; 25 jobs per page on sites with large schedules\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Duration sparkline\u003C\u002Fstrong> — tiny trend line per hook so a creeping-up execution time is visible before it becomes a timeout\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Execution Log\u003C\u002Fstrong> — persistent log of run history with duration and pass\u002Ffail status; retention is configurable\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hook and status filters\u003C\u002Fstrong> — search by hook name or narrow the table to just Overdue\u002FFailing\u002FHealthy\u002FNever Run\u003C\u002Fli>\n\u003Cli>\u003Cstrong>DISABLE_WP_CRON warning\u003C\u002Fstrong> — alerts you when automatic cron execution is disabled\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email and webhook alerts\u003C\u002Fstrong> — get notified after N consecutive failed runs or when a job has been overdue too long, with optional per-job thresholds and a one-click snooze for incidents you already know about. Webhook payloads work directly with Slack and Discord, no relay needed — setup instructions are built into the Settings tab\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Built-in SMTP settings\u003C\u002Fstrong> — route alert emails through your own mail provider instead of the server’s default mail() function, no separate SMTP plugin required\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email Log\u003C\u002Fstrong> — see every alert\u002Ftest email Cron Pulse has sent, with delivery status and the underlying error if one failed\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email Debug Log\u003C\u002Fstrong> — the raw SMTP conversation (connection, TLS, auth, server responses) for diagnosing delivery problems beyond a generic failure message — credentials are never written to it\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Send Test Email \u002F Send Test Webhook\u003C\u002Fstrong> — confirm your notification settings actually work before you need them\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP-CLI support\u003C\u002Fstrong> — \u003Ccode>wp cronpulse status\u003C\u002Fcode> for scripting health checks across sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>REST API\u003C\u002Fstrong> — \u003Ccode>GET \u002Fwp-json\u002Fcronpulse\u002Fv1\u002Fstatus\u003C\u002Fcode> for remote dashboards, authenticated like any other WP REST route\u003C\u002Fli>\n\u003Cli>Zero external dependencies — pure PHP and vanilla jQuery\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Who is this for?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WordPress developers\u003C\u002Fstrong> debugging cron-based features\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agencies\u003C\u002Fstrong> maintaining multiple client sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enterprise teams\u003C\u002Fstrong> needing visibility into scheduled background tasks\u003C\u002Fli>\n\u003Cli>Anyone tired of checking wp-cron manually or reading cryptic log files\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin stores cron execution data (hook name, timestamp, duration) in the WordPress options table. No data is sent externally unless you explicitly configure a webhook URL under alert settings, in which case alert payloads are POSTed to that URL. The REST API endpoint is read-only and pull-based — nothing is sent anywhere on its own. If you enable SMTP, your SMTP credentials are stored in the WordPress options table, same as any other plugin setting — no third-party service receives them except the SMTP server you configure. The email log stores recipient addresses and subjects for emails Cron Pulse has sent. All data is deleted on plugin uninstall.\u003C\u002Fp>\n","A visual dashboard to monitor, debug, and manually trigger WordPress cron jobs.",57,"2026-07-14T19:40:00.000Z",[120,121,20,21,122],"cron","cron-jobs","wp-cron","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcronpulse\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcronpulse.1.1.0.zip",{"attackSurface":126,"codeSignals":193,"taintFlows":202,"riskAssessment":203,"analyzedAt":209},{"hooks":127,"ajaxHandlers":178,"restRoutes":189,"shortcodes":190,"cronEvents":191,"entryPointCount":192,"unprotectedCount":11},[128,134,139,144,149,153,156,159,163,166,169,173],{"type":129,"name":130,"callback":131,"file":132,"line":133},"filter","manage_pages_columns","taiji_add_column","admin\u002Fcolumns.php",14,{"type":135,"name":136,"callback":137,"priority":101,"file":132,"line":138},"action","manage_pages_custom_column","taiji_render_column",35,{"type":135,"name":140,"callback":141,"file":142,"line":143},"admin_menu","taiji_register_admin_page","admin\u002Fdashboard.php",7,{"type":135,"name":145,"callback":146,"priority":101,"file":147,"line":148},"save_post","taiji_maybe_flush_cache_on_post_save","includes\u002Fdatabase.php",105,{"type":135,"name":150,"callback":151,"file":147,"line":152},"deleted_post","taiji_maybe_flush_cache_on_post_delete",106,{"type":135,"name":154,"callback":151,"file":147,"line":155},"trashed_post",107,{"type":135,"name":157,"callback":151,"file":147,"line":158},"untrashed_post",108,{"type":135,"name":160,"callback":161,"priority":101,"file":147,"line":162},"added_post_meta","taiji_maybe_flush_cache_on_template_meta_change",109,{"type":135,"name":164,"callback":161,"priority":101,"file":147,"line":165},"updated_post_meta",110,{"type":135,"name":167,"callback":161,"priority":101,"file":147,"line":168},"deleted_post_meta",111,{"type":135,"name":170,"callback":171,"file":147,"line":172},"switch_theme","taiji_flush_cache",112,{"type":135,"name":174,"callback":175,"priority":13,"file":176,"line":177},"admin_enqueue_scripts","taiji_admin_assets","taiji-template-inspector.php",55,[179,185],{"action":180,"nopriv":181,"callback":182,"hasNonce":183,"hasCapCheck":183,"file":184,"line":143},"taiji_load_posts",false,"taiji_ajax_load_posts",true,"admin\u002Fajax.php",{"action":186,"nopriv":181,"callback":187,"hasNonce":183,"hasCapCheck":183,"file":184,"line":188},"taiji_export_csv","taiji_ajax_export_csv",8,[],[],[],2,{"dangerousFunctions":194,"sqlUsage":195,"outputEscaping":198,"fileOperations":14,"externalRequests":11,"nonceChecks":192,"capabilityChecks":192,"bundledLibraries":201},[],{"prepared":196,"raw":11,"locations":197},12,[],{"escaped":199,"rawEcho":11,"locations":200},87,[],[],[],{"summary":204,"deductions":205},"The taiji-template-inspector v1.0.0 plugin exhibits a strong security posture based on the provided static analysis and vulnerability history. The absence of dangerous functions, the exclusive use of prepared statements for SQL queries, and 100% proper output escaping demonstrate excellent secure coding practices.  Furthermore, the presence of nonce and capability checks on all identified entry points, coupled with zero taint flows and no known vulnerabilities (CVEs), suggests a well-developed and secure plugin at this version.\n\nWhile the code analysis reveals a clean slate regarding common vulnerabilities like unescaped output or raw SQL, the presence of file operations warrants a cautious note. Although not inherently a vulnerability, it represents a potential attack vector if not handled with extreme care. The lack of external HTTP requests is a positive sign, reducing the risk of supply chain attacks or issues with external dependencies. The plugin's history of zero vulnerabilities further reinforces its current security. Overall, taiji-template-inspector v1.0.0 appears to be a secure plugin with good development practices and a clean security record.",[206],{"reason":207,"points":208},"File operations present in code",5,"2026-04-16T13:00:22.176Z",{"wat":211,"direct":220},{"assetPaths":212,"generatorPatterns":215,"scriptPaths":216,"versionParams":217},[213,214],"\u002Fwp-content\u002Fplugins\u002Ftaiji-template-inspector\u002Fassets\u002Fadmin.css","\u002Fwp-content\u002Fplugins\u002Ftaiji-template-inspector\u002Fassets\u002Fadmin.js",[],[214],[218,219],"taiji-template-inspector\u002Fassets\u002Fadmin.css?ver=","taiji-template-inspector\u002Fassets\u002Fadmin.js?ver=",{"cssClasses":221,"htmlComments":231,"htmlAttributes":232,"restEndpoints":235,"jsGlobals":236,"shortcodeOutput":238},[222,223,224,225,226,227,228,229,230],"taiji-empty-state","taiji-dropdown-list","taiji-dropdown-item","taiji-dropdown-item-main","taiji-dropdown-item-title","taiji-dropdown-item-meta","taiji-dropdown-actions","taiji-button","taiji-button-secondary",[],[233,234],"data-template","data-lang",[],[237],"taiji_ajax",[239,240,241,242,243,244,245,246,247,248,249,250,251,252],"\u003Cdiv class=\"taiji-empty-state\">","\u003Cspan class=\"dashicons dashicons-search\">\u003C\u002Fspan>","\u003Cp>No results\u003C\u002Fp>","\u003Cdiv class=\"taiji-dropdown-list\">","\u003Cdiv class=\"taiji-dropdown-item\">","\u003Cdiv class=\"taiji-dropdown-item-main\">","\u003Cdiv class=\"taiji-dropdown-item-title\">","\u003Cdiv class=\"taiji-dropdown-item-meta\">","\u003Cdiv class=\"taiji-dropdown-actions\">","\u003Ca class=\"button button-small taiji-button taiji-button-secondary\"","\u003Cspan class=\"dashicons dashicons-edit\">\u003C\u002Fspan>","\u003Cspan>Edit\u003C\u002Fspan>","\u003Cspan class=\"dashicons dashicons-external\">\u003C\u002Fspan>","\u003Cspan>View\u003C\u002Fspan>",{"error":183,"url":254,"statusCode":255,"statusMessage":256,"message":256},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Ftaiji-template-inspector\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":11,"versions":258},[]]