[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fgiwJ3eorJ0rnq7LmqNCL0pzFWCVFvSRHOtTIe1WufdQ":3},{"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":22,"download_link":23,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":36,"analysis":136,"fingerprints":177},"safe-activate","Safe Activate","1.0.1","Suman Biswas","https:\u002F\u002Fprofiles.wordpress.org\u002Fsumanbiswas013\u002F","\u003Cp>Safe Activate protects your WordPress site from plugin activation failures.\u003C\u002Fp>\n\u003Cp>When a plugin causes a fatal error during activation, Safe Activate automatically:\u003Cbr \u002F>\n* Detects the error\u003Cbr \u002F>\n* Deactivates the problematic plugin\u003Cbr \u002F>\n* Restores admin access\u003Cbr \u002F>\n* Logs the incident for review\u003C\u002Fp>\n\u003Cp>This helps prevent white screen errors and saves time troubleshooting plugin conflicts.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Automatic detection of fatal plugin errors\u003C\u002Fli>\n\u003Cli>Safe auto-deactivation of conflicting plugins\u003C\u002Fli>\n\u003Cli>Conflict activity logging\u003C\u002Fli>\n\u003Cli>Simple and lightweight\u003C\u002Fli>\n\u003Cli>No configuration required\u003C\u002Fli>\n\u003C\u002Ful>\n","Detects fatal errors during plugin activation and helps admins identify and safely resolve plugin conflicts without automatic actions.",0,120,"2026-02-11T16:02:00.000Z","6.9.4","5.5","7.2",[18,19,20,21],"fatal-error","plugin-activation","plugin-conflict","site-recovery","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsafe-activate\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsafe-activate.1.0.1.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"sumanbiswas013",3,60,93,30,89,"2026-04-04T16:19:48.994Z",[37,62,77,96,115],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":59,"download_link":60,"security_score":61,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"check-conflicts","Check Conflicts","1.1.6","ioannup","https:\u002F\u002Fprofiles.wordpress.org\u002Fioannup\u002F","\u003Cp>The plugin allows you to disable\u002Fenable plugins and\u002For activate a default theme for checking conflict between them \u003Cstrong>only for your IP\u003C\u002Fstrong>; other users won’t see any changes during the tests.\u003C\u002Fp>\n\u003Cp>It is made for developers, techical support engineers, as well as for regular WordPress users. Sometimes, usually after updating your plugins, themes or WordPress installation, strange issues may appear and mess the things up. This plugin provides a really neat way to check the problem.\u003C\u002Fp>\n\u003Ch3>Plugin Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Change active plugins only for your IP\u003C\u002Fli>\n\u003Cli>Change active theme only for your IP\u003C\u002Fli>\n\u003Cli>Add additional IPs to apply these settings\u003C\u002Fli>\n\u003Cli>Reset settings\u003C\u002Fli>\n\u003Cli>Support Multisites\u003C\u002Fli>\n\u003C\u002Ful>\n","The plugin allows you to disable\u002Fenable plugins and\u002For activate a default theme for checking conflict between them only for your IP; other users won&# …",1000,21152,94,18,"2023-11-07T16:20:00.000Z","6.4.8","5.0","5.6",[54,55,56,57,58],"check-plugin-conflicts","conflicts","debug","health-check","plugin-conflicts","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcheck-conflicts\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcheck-conflicts.1.1.6.zip",85,{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":11,"num_ratings":11,"last_updated":72,"tested_up_to":14,"requires_at_least":73,"requires_php":52,"tags":74,"homepage":75,"download_link":76,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"disable-fatal-error-handler","Disable Fatal Error Handler","0.0.4","Jose Mortellaro","https:\u002F\u002Fprofiles.wordpress.org\u002Fgiuse\u002F","\u003Cp>Activating Disable Fatal Error Handler your website will not send any email in case of fatal errors.\u003C\u002Fp>\n\u003Cp>When you work on a website and you don’t want the administrators receive an email every time the website triggers a fatal error, just activate this plugin.\u003C\u002Fp>\n\u003Cp>Disable Fatal Error Handler adds a constant in wp-config.php. You would not need this plugin if you remembered that constant and you have access via FTP.\u003C\u002Fp>\n\u003Cp>In my case I prefer remembering “Disable Fatal Error Handler”, search it in the plugins page, install and activate it, and that’s it.\u003C\u002Fp>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>If you need help open a thread on the support forum of this plugin.\u003Cbr \u002F>\nPlease, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">this detailed tutorial\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">how to enable debugging in WordPress\u003C\u002Fa> to learn more.\u003C\u002Fp>\n","Your website will not send any email in case of fatal errors.",200,2626,"2025-12-05T08:48:00.000Z","4.6",[63],"https:\u002F\u002Fjosemortellaro.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-fatal-error-handler.0.0.4.zip",{"slug":78,"name":79,"version":16,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":24,"downloaded":84,"rating":85,"num_ratings":86,"last_updated":87,"tested_up_to":14,"requires_at_least":88,"requires_php":52,"tags":89,"homepage":94,"download_link":95,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"conflict-finder-wp-fix-it","Conflict Finder","WP Fix It - WordPress Experts","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpfixit\u002F","\u003Cp>Conflict Finder is a comprehensive troubleshooting plugin designed for WordPress administrators, developers, and support professionals who need to identify the root cause of site issues.\u003C\u002Fp>\n\u003Cp>From a single interface, Conflict Finder allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable and manage WP_DEBUG without manually editing files\u003C\u002Fli>\n\u003Cli>View, download, and clear the WordPress debug log\u003C\u002Fli>\n\u003Cli>Temporarily disable plugins to identify conflicts\u003C\u002Fli>\n\u003Cli>Switch themes to test theme-related issues\u003C\u002Fli>\n\u003Cli>Test WordPress email delivery using \u003Ccode>wp_mail()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Important:\u003C\u002Fstrong>\u003Cbr \u002F>\nConflict Finder \u003Cstrong>does temporarily affect site behavior\u003C\u002Fstrong> while troubleshooting is active. This may include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disabled plugins\u003C\u002Fli>\n\u003Cli>A different active theme\u003C\u002Fli>\n\u003Cli>Debug notices or errors being displayed\u003C\u002Fli>\n\u003Cli>Changes visible to logged-out visitors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For this reason, troubleshooting should be performed during maintenance windows or on staging sites whenever possible.\u003C\u002Fp>\n\u003Cp>Conflict Finder automatically tracks your original configuration and allows you to restore plugins, themes, and debugging settings once testing is complete.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Troubleshooting Dashboard\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Central overview of debugging and conflict states\u003C\u002Fli>\n\u003Cli>Environment snapshot including WordPress, PHP, memory, and server software\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>WP_DEBUG Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable or disable WP_DEBUG with a single switch\u003C\u002Fli>\n\u003Cli>Control error display and logging behavior\u003C\u002Fli>\n\u003Cli>Load unminified scripts for debugging\u003C\u002Fli>\n\u003Cli>View, download, or clear \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Safely updates \u003Ccode>wp-config.php\u003C\u002Fcode> as needed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Plugin Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily deactivate all active plugins\u003C\u002Fli>\n\u003Cli>Save and restore original plugin states\u003C\u002Fli>\n\u003Cli>Activate plugins one at a time to identify conflicts\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Theme Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily switch to another installed theme\u003C\u002Fli>\n\u003Cli>Identify theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Restore the original theme instantly\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Email Delivery Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Send a real test email using WordPress mail\u003C\u002Fli>\n\u003Cli>Confirm whether the server can successfully send email\u003C\u002Fli>\n\u003Cli>Helps identify SMTP or hosting mail issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>When to Use Conflict Finder\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Diagnosing white screens or fatal errors\u003C\u002Fli>\n\u003Cli>Identifying plugin conflicts\u003C\u002Fli>\n\u003Cli>Testing theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Investigating PHP notices or warnings\u003C\u002Fli>\n\u003Cli>Verifying WordPress email delivery\u003C\u002Fli>\n\u003Cli>Support and development workflows\u003C\u002Fli>\n\u003C\u002Ful>\n","Conflict Finder is a WordPress troubleshooting toolkit that helps diagnose plugin conflicts, theme issues, debugging errors, and email delivery proble …",8747,90,4,"2026-01-27T14:26:00.000Z","4.9",[90,20,91,92,93],"debug-log","theme-conflict","troubleshooting","wp_debug","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fconflict-finder-wp-fix-it.7.2.zip",{"slug":97,"name":98,"version":99,"author":100,"author_profile":101,"description":102,"short_description":103,"active_installs":85,"downloaded":104,"rating":24,"num_ratings":105,"last_updated":106,"tested_up_to":107,"requires_at_least":108,"requires_php":109,"tags":110,"homepage":113,"download_link":114,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"custom-recovery-mode-email","Custom Recovery Mode Email","1.0.6","Jairo Ochoa","https:\u002F\u002Fprofiles.wordpress.org\u002Fjairoochoa\u002F","\u003Cp>Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with an automated email.\u003C\u002Fp>\n\u003Cp>But sometimes the message bothers people who don’t know how to handle with it and how to fix the bug which causes the crash.\u003C\u002Fp>\n\u003Cp>With \u003Cem>Custom Recovery Mode Email\u003C\u002Fem> now you can choose the right recipient email of the person who can deal with it.\u003C\u002Fp>\n\u003Cp>Optionally you can also set Email and Name sender.\u003C\u002Fp>\n\u003Ch3>Translations\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Español (España)\u003C\u002Fli>\n\u003Cli>Euskara (thanks to @garridinsi)\u003C\u002Fli>\n\u003Cli>Galego\u003C\u002Fli>\n\u003Cli>Svenska (thanks to @tobifjellner)\u003C\u002Fli>\n\u003C\u002Ful>\n","Change the recipient address when WordPress sends an email if a Fatal Error occurs.",2460,1,"2025-08-05T19:33:00.000Z","6.8.5","6.0","7.4",[18,111,112],"recovery-mode","recovery-mode-email","https:\u002F\u002Fwww.dixitalmedia.com\u002F#que-hacemos","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-recovery-mode-email.zip",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":123,"downloaded":124,"rating":24,"num_ratings":125,"last_updated":126,"tested_up_to":107,"requires_at_least":127,"requires_php":128,"tags":129,"homepage":134,"download_link":135,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"fatal-plugin-auto-deactivator","Fatal Plugin Auto Deactivator – Never let a plugin break your site","1.1.0","Linkon Miyan","https:\u002F\u002Fprofiles.wordpress.org\u002Frudlinkon\u002F","\u003Cp>The Fatal Plugin Auto Deactivator plugin is a powerful tool designed to enhance the stability and reliability of your WordPress website. It automatically detects and deactivates plugins that cause fatal errors, preventing your entire site from crashing and becoming inaccessible.\u003C\u002Fp>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automatic Error Detection\u003C\u002Fstrong>: Monitors for fatal PHP errors in real-time using WordPress drop-in technology\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Smart Plugin Identification\u003C\u002Fstrong>: Identifies which plugin is causing the fatal error through stack trace analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Instant Deactivation\u003C\u002Fstrong>: Automatically deactivates the problematic plugin during the shutdown phase\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detailed Admin Notifications\u003C\u002Fstrong>: Provides clear notifications about which plugin was deactivated and why\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Persistent Error Logging\u003C\u002Fstrong>: Records detailed information about errors in a permanent log for troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Error Log Management Page\u003C\u002Fstrong>: Dedicated admin page to view, manage, and clear error logs with detailed history\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Zero Configuration\u003C\u002Fstrong>: Works right out of the box with no setup required\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Error Page\u003C\u002Fstrong>: Displays a user-friendly error page with a reload button instead of the white screen of death\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug-Aware Display\u003C\u002Fstrong>: Shows detailed error information only when WP_DEBUG_DISPLAY is enabled for security\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Drop-in Management\u003C\u002Fstrong>: Automatically installs and manages WordPress fatal-error-handler.php drop-in\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>How It Works\u003C\u002Fh3>\n\u003Cp>This plugin uses WordPress’s built-in drop-in system to provide the most reliable error handling possible. When activated, it:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Installs a Drop-in\u003C\u002Fstrong>: Creates a \u003Ccode>fatal-error-handler.php\u003C\u002Fcode> file in your wp-content directory\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Monitors for Errors\u003C\u002Fstrong>: WordPress automatically uses this drop-in when fatal errors occur\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Captures Error Details\u003C\u002Fstrong>: Records the error message, file, and line number during the shutdown phase\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Identifies the Plugin\u003C\u002Fstrong>: Analyzes the error stack trace to determine which plugin caused the issue\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deactivates Safely\u003C\u002Fstrong>: Automatically deactivates only the problematic plugin\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logs Everything\u003C\u002Fstrong>: Stores detailed error information in a permanent log for troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Notifies Admins\u003C\u002Fstrong>: Displays clear admin notices with error details when you next log in\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shows User-Friendly Pages\u003C\u002Fstrong>: Displays a custom error page with reload button instead of the white screen of death\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The drop-in approach ensures maximum reliability since it operates at the WordPress core level, even when other plugins fail.\u003C\u002Fp>\n\u003Ch3>Use Cases\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Development Environments\u003C\u002Fstrong>: Test new plugins without worrying about site crashes\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Production Sites\u003C\u002Fstrong>: Add an extra layer of protection against unexpected plugin conflicts\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Managed WordPress\u003C\u002Fstrong>: Essential tool for agencies and freelancers managing multiple client sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WooCommerce Stores\u003C\u002Fstrong>: Prevent revenue loss from site downtime due to plugin errors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Why You Need This Plugin\u003C\u002Fh3>\n\u003Cp>WordPress fatal errors can make your entire site inaccessible, requiring FTP or hosting panel access to fix. With Fatal Plugin Auto Deactivator, your site remains operational even when a plugin causes a critical error, giving you time to address the issue without emergency measures.\u003C\u002Fp>\n","Automatically deactivates plugins that cause fatal errors to prevent site crashes and keep your WordPress site running smoothly.",50,764,2,"2025-06-01T03:28:00.000Z","5.3","7.0",[130,131,18,132,133],"crash-prevention","error-handling","plugin-deactivation","site-protection","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffatal-plugin-auto-deactivator\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffatal-plugin-auto-deactivator.1.1.0.zip",{"attackSurface":137,"codeSignals":157,"taintFlows":169,"riskAssessment":170,"analyzedAt":176},{"hooks":138,"ajaxHandlers":153,"restRoutes":154,"shortcodes":155,"cronEvents":156,"entryPointCount":11,"unprotectedCount":11},[139,145,149],{"type":140,"name":141,"callback":142,"file":143,"line":144},"action","admin_menu","menu","includes\\class-sa-admin.php",7,{"type":140,"name":146,"callback":147,"file":143,"line":148},"admin_notices","notice",8,{"type":140,"name":150,"callback":151,"file":152,"line":144},"activated_plugin","track_plugin","includes\\class-sa-plugin-watcher.php",[],[],[],[],{"dangerousFunctions":158,"sqlUsage":159,"outputEscaping":165,"fileOperations":11,"externalRequests":11,"nonceChecks":105,"capabilityChecks":11,"bundledLibraries":168},[],{"prepared":160,"raw":105,"locations":161},6,[162],{"file":143,"line":163,"context":164},45,"$wpdb->query() with variable interpolation",{"escaped":166,"rawEcho":11,"locations":167},9,[],[],[],{"summary":171,"deductions":172},"The \"safe-activate\" plugin v1.0.1 demonstrates a generally strong security posture based on the provided static analysis.  It exhibits good practices such as 100% output escaping and a high percentage of SQL queries using prepared statements. Furthermore, the absence of known vulnerabilities in its history is a significant positive indicator. The plugin also has no apparent external attack surface through common entry points like AJAX, REST API, shortcodes, or cron events, and no file operations or external HTTP requests were detected.  There is also a nonce check present, which is a good security practice.\n\nHowever, there are a couple of minor concerns.  The most notable is the complete lack of capability checks. While there are no identified entry points that are currently unprotected, this absence means that even if new entry points were inadvertently introduced in future versions without proper authorization checks, they would be inherently vulnerable. The presence of 7 SQL queries, even with high prepared statement usage, still represents a potential area for subtle issues if not handled with extreme care. Taint analysis also showed zero flows, which is excellent but may indicate a very limited scope or complexity in the plugin's operations.\n\nOverall, \"safe-activate\" v1.0.1 appears to be a secure plugin with a commendable emphasis on preventing common web vulnerabilities. The lack of historical vulnerabilities and the robust static analysis findings suggest a well-developed and tested codebase. The primary area for improvement is the implementation of capability checks to further strengthen its authorization model against potential future attack vectors.",[173],{"reason":174,"points":175},"No capability checks implemented",10,"2026-03-17T06:16:40.362Z",{"wat":178,"direct":187},{"assetPaths":179,"generatorPatterns":182,"scriptPaths":183,"versionParams":184},[180,181],"\u002Fwp-content\u002Fplugins\u002Fsafe-activate\u002Fincludes\u002Fcss\u002Fsafe-activate.css","\u002Fwp-content\u002Fplugins\u002Fsafe-activate\u002Fincludes\u002Fjs\u002Fsafe-activate.js",[],[181],[185,186],"safe-activate\u002Fincludes\u002Fcss\u002Fsafe-activate.css?ver=","safe-activate\u002Fincludes\u002Fjs\u002Fsafe-activate.js?ver=",{"cssClasses":188,"htmlComments":189,"htmlAttributes":190,"restEndpoints":191,"jsGlobals":192,"shortcodeOutput":193},[],[],[],[],[],[]]