[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fGlRTZ5kQGOpUPad-22hzuFammiFpmN5Tdh9H6k5RpgM":3,"$fe9zdht_lbQ2cQbcCru1rfA65rh-xXyXGkPkdlEjslSA":136,"$fOj5PgXZgPJvru_q8o_uY7t2U4_qvQo3QXMXZ-ElJM_0":141},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":38,"analysis":26,"fingerprints":26},"outradar","OutRadar","1.0.1","Nilambar Sharma","https:\u002F\u002Fprofiles.wordpress.org\u002Fnilambar\u002F","\u003Cp>OutRadar hooks into WordPress’s HTTP layer and records every outbound request — URL, method, status code, response size, originating plugin or theme, and execution context (frontend, admin, cron, CLI).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Logs all outbound HTTP requests via \u003Ccode>WP_HTTP\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Attributes each request to its source plugin or theme\u003C\u002Fli>\n\u003Cli>Filterable, paginated request log in the admin\u003C\u002Fli>\n\u003Cli>Dashboard with request counts, domain breakdown, and context chart\u003C\u002Fli>\n\u003Cli>CSV and JSON export\u003C\u002Fli>\n\u003Cli>Configurable log retention (7 days, 30 days, 90 days, or forever)\u003C\u002Fli>\n\u003Cli>Source exclusion list to suppress noisy plugins\u003C\u002Fli>\n\u003C\u002Ful>\n","Log outbound HTTP requests from WordPress plugins, themes, and core.",0,112,"2026-07-07T07:12:00.000Z","7.0.2","6.9","7.4",[18,19,20,21,22],"debug","http","logging","monitoring","requests","https:\u002F\u002Fgithub.com\u002Fernilambar\u002Foutradar","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Foutradar.1.0.1.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"nilambar",10,8860,98,22,93,"2026-08-29T02:50:59.655Z",[39,62,80,94,115],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":25,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":59,"download_link":60,"security_score":61,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"debug-bar-remote-requests","Debug Bar Remote Requests","0.1.2","Matthew Boynes","https:\u002F\u002Fprofiles.wordpress.org\u002Fmboynes\u002F","\u003Cp>An add-on for the Debug Bar plugin that will log and profile remote requests made through the HTTP API. This plugin requires the Debug Bar Plugin.\u003C\u002Fp>\n\u003Cp>This plugin will add a “Remote Requests” panel to Debug Bar that will display the:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Request method (GET, POST, etc)\u003C\u002Fli>\n\u003Cli>URL\u003C\u002Fli>\n\u003Cli>Time per request\u003C\u002Fli>\n\u003Cli>Total time for all requests\u003C\u002Fli>\n\u003Cli>Total number of requests\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Optionally, you can add ?dbrr_full=1 to your URL to get additional information, including all request parameters and a full dump of the response with headers.\u003C\u002Fp>\n","An add-on for the Debug Bar plugin that will log and profile remote requests made through the HTTP API",20,26472,1,"2014-04-23T20:31:00.000Z","3.9.40","3.5","",[55,18,56,57,58],"api","debug-bar","http-api","remote-requests","http:\u002F\u002Fgithub.com\u002Falleyinteractive.com\u002Fdebug-bar-remote-requests","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-remote-requests.0.1.2.zip",85,{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":11,"downloaded":70,"rating":11,"num_ratings":11,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":74,"tags":75,"homepage":78,"download_link":79,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"dockthor","DockTHOR","1.0.0","Jacek Sultan","https:\u002F\u002Fprofiles.wordpress.org\u002Fjacycha\u002F","\u003Cp>DockTHOR integrates WordPress with the THOR monitoring platform and automatically reports PHP errors and uncaught exceptions.\u003C\u002Fp>\n\u003Cp>The plugin is designed to work silently in the background and has no admin interface. After installation you only need to configure your THOR project credentials.\u003C\u002Fp>\n\u003Ch3>Features:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Automatic reporting of PHP errors and uncaught exceptions\u003C\u002Fli>\n\u003Cli>Support for custom error filtering\u003C\u002Fli>\n\u003Cli>Optional user context information\u003C\u002Fli>\n\u003Cli>Customizable configuration via WordPress constants and filters\u003C\u002Fli>\n\u003Cli>Minimal performance overhead\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin is intended for developers and teams who want to monitor errors occurring in WordPress installations.\u003C\u002Fp>\n\u003Cp>Installation\u003C\u002Fp>\n\u003Col>\n\u003Cli>Upload the plugin files to the \u003Ccode>\u002Fwp-content\u002Fplugins\u002Fdockthor\u003C\u002Fcode> directory, or install the plugin through the WordPress plugins screen.\u003C\u002Fli>\n\u003Cli>Activate the plugin through the \u003Cstrong>Plugins\u003C\u002Fstrong> menu in WordPress.\u003C\u002Fli>\n\u003Cli>Configure your THOR credentials in \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Example configuration:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\ndefine( 'DOCK_THOR_TOKEN', 'YOUR_THOR_TOKEN' );\u003Cbr \u002F>\ndefine( 'DOCK_THOR_PRIVATE_KEY', 'YOUR_PRIVATE_KEY' );\u003C\u002Fcode>\u003Cbr \u002F>\nOnce configured, the plugin will automatically begin reporting PHP errors.\u003C\u002Fp>\n\u003Cp>Configuration\u003C\u002Fp>\n\u003Cp>Add the following constants to your \u003Ccode>wp-config.php\u003C\u002Fcode> file.\u003C\u002Fp>\n\u003Ch3>DockTHOR Token\u003C\u002Fh3>\n\u003Cp>\u003Ccode>php\u003Cbr \u002F>\ndefine( 'DOCK_THOR_TOKEN', 'YOUR_THOR_TOKEN' );\u003Cbr \u002F>\n    `\u003Ch3>Private Key\u003C\u002Fh3>\u003C\u002Fcode>php\u003Cbr \u002F>\ndefine( ‘DOCK_THOR_PRIVATE_KEY’, ‘YOUR_PRIVATE_KEY’ );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch3>Error Types (optional)\u003C\u002Fh3>\n\u003Cp>“`php\u003Cbr \u002F>\ndefine( ‘DOCK_THOR_ERROR_TYPES’, E_ALL & ~E_DEPRECATED & ~E_NOTICE & ~E_USER_DEPRECATED );\u003Cbr \u002F>\n    \u003Ccode>Define which PHP errors should be captured.\u003Ch3>Send Default PII (optional)\u003C\u002Fh3>\u003Cbr \u002F>\nIf enabled, additional context such as the logged-in user and IP address will be attached to the event.\u003C\u002Fcode>php\u003Cbr \u002F>\ndefine( ‘DOCK_THOR_SEND_DEFAULT_PII’, true );\u003Cbr \u002F>\n    \u003Ccode>\u003Ch3>Site Version (optional)\u003C\u002Fh3>\u003Cbr \u002F>\nDefine the version of your website. This can help track which version of the site generated an error.\u003C\u002Fcode>php\u003Cbr \u002F>\ndefine( ‘DOCK_THOR_VERSION’, ‘v1.0.0’ );\u003Cbr \u002F>\n    \u003Ccode>\u003Ch3>Environment (optional)\u003C\u002Fh3>\u003Cbr \u002F>\nDefine the current environment.\u003C\u002Fcode>php\u003Cbr \u002F>\ndefine( ‘DOCK_THOR_ENV’, ‘production’ );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>Filters\u003C\u002Fp>\n\u003Cp>DockTHOR provides several filters that allow developers to customize behavior.\u003C\u002Fp>\n\u003Ch3>dock_thor_user_context\u003C\u002Fh3>\n\u003Cp>Allows extending the user context sent to THOR.\u003C\u002Fp>\n\u003Cp>Example:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'dock_thor_user_context', function ( array $user ) {\u003Cbr \u002F>\n    return array_merge( $user, ['custom_meta' => 'value'] );\u003Cbr \u002F>\n});\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Note: These values may be exposed publicly when used in JavaScript trackers.\u003C\u002Fp>\n\u003Ch3>dock_thor_token\u003C\u002Fh3>\n\u003Cp>Allows overriding the THOR token.\u003C\u002Fp>\n\u003Cp>Example:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'dock_thor_token', function ( $token ) {\u003Cbr \u002F>\n    return 'xxxxxxxxxxxxxxxxxxxx';\u003Cbr \u002F>\n});\u003C\u002Fcode>\u003Cbr \u002F>\nUsing the \u003Ccode>DOCK_THOR_TOKEN\u003C\u002Fcode> constant is recommended instead.\u003C\u002Fp>\n\u003Ch3>dock_thor_scope\u003C\u002Fh3>\n\u003Cp>Allows modifying the THOR scope before events are sent.\u003C\u002Fp>\n\u003Cp>Example:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'dock_thor_scope', function ( \\Dock\\Thor\\State\\Scope $scope ) {\u003Cbr \u002F>\n    $scope->setTag('custom-tag', 'value');\u003Cbr \u002F>\n    return $scope;\u003Cbr \u002F>\n});\u003C\u002Fcode>\u003C\u002Fp>\n\u003Ch3>dock_thor_options\u003C\u002Fh3>\n\u003Cp>Allows customizing THOR SDK options.\u003C\u002Fp>\n\u003Cp>Example:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'dock_thor_options', function ( \\Dock\\Thor\\Options $options ) {\u003Cbr \u002F>\n    $options->setSampleRate(0.9);\u003Cbr \u002F>\n    return $options;\u003Cbr \u002F>\n});\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Advanced Usage\u003C\u002Fp>\n\u003Ch3>High volume of notices\u003C\u002Fh3>\n\u003Cp>Some plugins generate large amounts of PHP notices. You can filter them out:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\ndefine( 'DOCK_THOR_ERROR_TYPES', E_ALL & ~E_NOTICE );\u003C\u002Fcode>\u003C\u002Fp>\n\u003Ch3>Capturing handled exceptions\u003C\u002Fh3>\n\u003Cp>If you want to report handled exceptions:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\ntry {\u003Cbr \u002F>\n    myMethodThatCanThrowAnException();\u003Cbr \u002F>\n} catch ( \\Exception $e ) {\u003Cbr \u002F>\n    if ( function_exists( 'dock_thor_safe' ) ) {\u003Cbr \u002F>\n        dock_thor_safe( function ( \\Dock\\Thor\\State\\HubInterface $client ) use ( $e ) {\u003Cbr \u002F>\n            $client->captureException( $e );\u003Cbr \u002F>\n        });\u003Cbr \u002F>\n    }\u003Cbr \u002F>\n    wp_die( 'An error occurred.' );\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Frequently Asked Questions\u003C\u002Fp>\n\u003Ch4>Does this plugin have an admin panel?\u003C\u002Fh4>\n\u003Cp>No. DockTHOR works automatically after configuration in \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>Will this slow down my site?\u003C\u002Fh4>\n\u003Cp>The plugin is designed to have minimal performance impact. Error events are sent asynchronously when possible.\u003C\u002Fp>\n\u003Ch4>Can I disable certain errors?\u003C\u002Fh4>\n\u003Cp>Yes. You can configure the error types captured using the \u003Ccode>DOCK_THOR_ERROR_TYPES\u003C\u002Fcode> constant.\u003C\u002Fp>\n","DockTHOR is a lightweight WordPress integration for sending PHP errors and exceptions to the THOR monitoring platform.",213,"2026-03-24T17:04:00.000Z","6.9.5","5.6","7.2",[76,77,20,21],"debugging","error-tracking","https:\u002F\u002Fthor.dock.codes","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdockthor.1.0.0.zip",{"slug":81,"name":82,"version":65,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":11,"downloaded":87,"rating":25,"num_ratings":49,"last_updated":88,"tested_up_to":14,"requires_at_least":89,"requires_php":16,"tags":90,"homepage":92,"download_link":93,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"kaiizen-api-request-monitor","API Request Monitor: Monitor Incoming & Outgoing API Requests and Manage Webhooks","Huzoor Bux","https:\u002F\u002Fprofiles.wordpress.org\u002Fhuzoorbakhsh\u002F","\u003Cp>Kaiizen API Request Monitor is an advanced API monitoring and debugging plugin for WordPress. Track incoming REST API requests, outbound HTTP requests, webhook activity, API performance, authentication failures, and WooCommerce API events in real time.\u003C\u002Fp>\n\u003Cp>Whether you’re building custom integrations, troubleshooting API errors, testing endpoints, monitoring webhooks, or auditing API security, Kaiizen API Request Monitor provides the tools needed to understand exactly how data moves through your WordPress site.\u003C\u002Fp>\n\u003Cp>Perfect for:\u003C\u002Fp>\n\u003Cp>WordPress developers\u003Cbr \u002F>\nWooCommerce developers\u003Cbr \u002F>\nAPI integrators\u003Cbr \u002F>\nAgencies managing client websites\u003Cbr \u002F>\nDevOps and support teams\u003Cbr \u002F>\nPlugin and theme developers\u003C\u002Fp>\n\u003Ch4>Core Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Request Logger\u003C\u002Fstrong> — Logs all incoming WordPress REST API requests: method, endpoint, headers, body, response code, response time, user, and IP address.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Outbound Logger\u003C\u002Fstrong> — Intercepts all outbound HTTP requests made via \u003Ccode>wp_remote_*\u003C\u002Fcode> functions and logs URL, headers, payload, and response.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Webhook Logger\u003C\u002Fstrong> — Captures and logs both incoming and outgoing webhooks, including WooCommerce webhooks.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>API Explorer\u003C\u002Fstrong> — A built-in HTTP client that lets you build and fire REST requests (GET, POST, PUT, PATCH, DELETE) directly from your WordPress admin. Save requests as reusable templates.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Performance Analytics\u003C\u002Fstrong> — Dashboard with hourly request volume charts, slowest endpoints, most-used endpoints, requests per minute, and error rate metrics.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Monitor\u003C\u002Fstrong> — Detects brute-force API authentication failures and fires configurable alerts via Email, Slack, or Discord.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Activity Timeline\u003C\u002Fstrong> — WooCommerce integration that tracks order, product, customer, and coupon changes made through the REST API.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Security & Privacy\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>All logs are stored in your own database — no data is sent to external services unless you configure Slack or Discord webhook alerts.\u003C\u002Fli>\n\u003Cli>Configurable field masking automatically redacts sensitive keys (passwords, tokens, API keys, Authorization headers) from stored logs.\u003C\u002Fli>\n\u003Cli>Log retention is configurable (default: 30 days); old logs are pruned automatically via daily cron.\u003C\u002Fli>\n\u003Cli>Dashboard access is restricted to WordPress administrators (\u003Ccode>manage_options\u003C\u002Fcode> capability).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>External Services\u003C\u002Fh4>\n\u003Cp>This plugin can optionally send security alert notifications to third-party webhook services. This only happens when you explicitly configure a webhook URL in Settings and enable alerts.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Slack\u003C\u002Fstrong> — Alert payloads (event type and details) are sent to your configured Slack Incoming Webhook URL. Terms: https:\u002F\u002Fslack.com\u002Fterms-of-service | Privacy: https:\u002F\u002Fslack.com\u002Fprivacy-policy\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Discord\u003C\u002Fstrong> — Alert payloads (event type and details) are sent to your configured Discord Webhook URL. Terms: https:\u002F\u002Fdiscord.com\u002Fterms | Privacy: https:\u002F\u002Fdiscord.com\u002Fprivacy\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No data is transmitted to external services unless you configure these integrations.\u003C\u002Fp>\n\u003Ch4>Source Code\u003C\u002Fh4>\n\u003Cp>The plugin includes a compiled JavaScript bundle (\u003Ccode>build\u002Findex.js\u003C\u002Fcode>) generated from source files in the \u003Ccode>src\u002F\u003C\u002Fcode> directory using \u003Ccode>@wordpress\u002Fscripts\u003C\u002Fcode> (webpack). The full source is included in the plugin package under \u003Ccode>src\u002F\u003C\u002Fcode>. To rebuild: \u003Ccode>npm install && npm run build\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 6.0 or higher\u003C\u002Fli>\n\u003Cli>PHP 7.4 or higher\u003C\u002Fli>\n\u003Cli>WooCommerce (optional) — required only for the Activity Timeline and WooCommerce webhook logging features.\u003C\u002Fli>\n\u003C\u002Ful>\n","A developer-focused tool for monitoring, debugging, testing, and logging WordPress REST API requests and external API integrations.",202,"2026-06-19T17:52:00.000Z","6.0",[55,18,20,21,91],"rest-api","https:\u002F\u002Fhuzoorbux.com\u002Fkaiizen-api-request-monitor","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkaiizen-api-request-monitor.1.0.0.zip",{"slug":95,"name":96,"version":97,"author":98,"author_profile":99,"description":100,"short_description":101,"active_installs":102,"downloaded":103,"rating":34,"num_ratings":104,"last_updated":105,"tested_up_to":14,"requires_at_least":106,"requires_php":107,"tags":108,"homepage":113,"download_link":114,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"wp-sentry-integration","Sentry for WordPress","8.11.1","stayallive","https:\u002F\u002Fprofiles.wordpress.org\u002Fstayallive\u002F","\u003Cp>This plugin can report PHP errors and Browser (JavaScript) errors to Sentry.\u003C\u002Fp>\n\u003Cp>It will auto detect authenticated users and add context where possible. All context\u002Ftags can be adjusted\u002Fexpanded using filters.\u003C\u002Fp>\n\u003Cp>\u003Cem>For more information and documentation have a look at the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fstayallive\u002Fwp-sentry\u002Ftree\u002Fv8.11.1#readme\" rel=\"nofollow ugc\">full documentation\u003C\u002Fa>.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>Contributors\u003C\u002Fh3>\n\u003Cp>See: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fstayallive\u002Fwp-sentry\u002Fgraphs\u002Fcontributors\" rel=\"nofollow ugc\">github.com\u002Fstayallive\u002Fwp-sentry\u002Fgraphs\u002Fcontributors\u003C\u002Fa>\u003C\u002Fp>\n","A (unofficial) WordPress plugin to report PHP errors and Browser (JavaScript) errors to Sentry.",10000,910720,16,"2026-06-08T06:56:00.000Z","4.4","7.2.5",[109,110,111,20,112],"error-monitoring","error-handler","log","sentry","https:\u002F\u002Fgithub.com\u002Fstayallive\u002Fwp-sentry","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-sentry-integration.8.11.1.zip",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":123,"downloaded":124,"rating":125,"num_ratings":126,"last_updated":127,"tested_up_to":72,"requires_at_least":128,"requires_php":53,"tags":129,"homepage":132,"download_link":133,"security_score":134,"vuln_count":49,"unpatched_count":11,"last_vuln_date":135,"fetched_at":27},"bugsnag","BugSnag Error Monitoring plugin","2.0.0","SmartBear","https:\u002F\u002Fprofiles.wordpress.org\u002Fsmartbear\u002F","\u003Cp>Automatically detects errors & crashes on your WordPress site using BugSnag to notify you by email, chat or issues system.\u003C\u002Fp>\n\u003Cp>All websites crash from time to time, including WordPress sites! Th BugSnag Error Reporting plugin automatically detects crashes, exceptions and other errors in your WordPress PHP code as well as any errors in plugins you are using.\u003C\u002Fp>\n\u003Cp>Errors are sent to your \u003Ca href=\"https:\u002F\u002Fbugsnag.com\" rel=\"nofollow ugc\">BugSnag Dashboard\u003C\u002Fa> for you to view and debug, and we’ll also notify you by email, chat, sms or create a ticket in your issue tracking system if you use one. We’ll also show you exactly how many times each error occurred, and how many users were impacted by each crash.\u003C\u002Fp>\n","Automatically detects errors & crashes on your WordPress site using BugSnag to notify you by email, chat or issues system.",2000,118962,74,9,"2026-04-28T09:55:00.000Z","2.0",[116,130,131,20,21],"error","exception","https:\u002F\u002Fbugsnag.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbugsnag.2.0.0.zip",99,"2025-09-05 00:00:00",{"error":137,"url":138,"statusCode":139,"statusMessage":140,"message":140},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Foutradar\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":142,"versions":143},2,[144,150],{"version":6,"download_url":24,"svn_tag_url":145,"released_at":26,"has_diff":146,"diff_files_changed":147,"diff_lines":26,"trac_diff_url":148,"vulnerabilities":149,"is_current":137},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Foutradar\u002Ftags\u002F1.0.1\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Foutradar%2Ftags%2F1.0.0&new_path=%2Foutradar%2Ftags%2F1.0.1",[],{"version":65,"download_url":151,"svn_tag_url":152,"released_at":26,"has_diff":146,"diff_files_changed":153,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":154,"is_current":146},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Foutradar.1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Foutradar\u002Ftags\u002F1.0.0\u002F",[],[]]