[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$foGuP3sGGoU7vxwqoukMcUptB3R24snm2O-z1CTis3Rs":3},{"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":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":40,"analysis":125,"fingerprints":161},"pco-kint","PCo Kint","1.0.10","Compute","https:\u002F\u002Fprofiles.wordpress.org\u002Fcompute\u002F","\u003Cp>PCo-Kint is a simple WordPress plugin wrapper for \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fraveren\u002Fkint\u002F\" rel=\"nofollow ugc\">kint\u003C\u002Fa>, a pretty replacement for \u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.var-dump.php\" rel=\"nofollow ugc\">var_dump()\u003C\u002Fa>, \u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.print-r.php]\" rel=\"nofollow ugc\">print_r()\u003C\u002Fa> and \u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.debug-backtrace.php]\" rel=\"nofollow ugc\">debug_backtrace()\u003C\u002Fa>. Kint is also a great replacement to Krumo!\u003C\u002Fp>\n\u003Cp>Simply use the \u003Ccode>d()\u003C\u002Fcode> function to output your objects or arrays, or use \u003Ccode>ddd()\u003C\u002Fcode> if you want to terminate the current script.\u003C\u002Fp>\n\u003Cp>A great alternative to \u003Ccode>echo'\u003Cpre>';var_dump($var);die;\u003C\u002Fcode>!\u003C\u002Fp>\n\u003Cp>A full list of features can be found on the project page:\u003C\u002Fp>\n\u003Cp>http:\u002F\u002Fraveren.github.io\u002Fkint\u002F\u003C\u002Fp>\n\u003Cp>Contribute to \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FPeytz-WordPress\u002Fpco-kint\" rel=\"nofollow ugc\">this project\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FPeytz-WordPress\" rel=\"nofollow ugc\">github\u003C\u002Fa> or find \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fpeytzco\u002F\" rel=\"nofollow ugc\">all of our favorite and custom made plugins\u003C\u002Fa>\u003C\u002Fp>\n","Kint debugger for WordPress - a powerful and modern PHP debugging tool.",10,1983,100,1,"2015-10-28T13:13:00.000Z","4.3.34","3.5","",[20,21,22,23,24],"debug","kint","krumo","print_r","var_dump","https:\u002F\u002Fgithub.com\u002FPeytz-WordPress\u002Fpco-kint","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpco-kint.1.0.10.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":36,"avg_patch_time_days":37,"trust_score":38,"computed_at":39},"compute",6,330,90,30,87,"2026-04-05T01:23:51.154Z",[41,58,74,93,111],{"slug":42,"name":43,"version":44,"author":45,"author_profile":46,"description":47,"short_description":48,"active_installs":13,"downloaded":49,"rating":13,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":17,"requires_php":53,"tags":54,"homepage":56,"download_link":57,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"kint-php-debugger","Kint PHP Debugger","2.0.2","Tonya Mork","https:\u002F\u002Fprofiles.wordpress.org\u002Fhellofromtonya\u002F","\u003Cp>This WordPress plugin is a wrapper for the \u003Ca href=\"https:\u002F\u002Fkint-php.github.io\u002Fkint\u002F\" rel=\"nofollow ugc\">Kint\u003C\u002Fa> PHP Debugger utility version 1.x.  Now instead of using var_dump() or print_r(), you simply use d() with zero, nadda, no formatting required.\u003C\u002Fp>\n\u003Cp>Use this tool when you are debugging your website, in place of \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.var-dump.php\" rel=\"nofollow ugc\">var_dump()\u003C\u002Fa>\u003C\u002Fstrong>, \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.print-r.php\" rel=\"nofollow ugc\">print_r()\u003C\u002Fa>\u003C\u002Fstrong> and \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.debug-backtrace.php\" rel=\"nofollow ugc\">debug_backtrace()\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch4>Handy Tools\u003C\u002Fh4>\n\u003Cp>Some handy tools just for the PHP Developer:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>d( $var );\u003C\u002Fcode> to render a collapsible UI container which displays your variable data in “the most informative way”\u003C\u002Fli>\n\u003Cli>\u003Ccode>ddd( $var );\u003C\u002Fcode> same as d() except that it also executes \u003Ccode>die()\u003C\u002Fcode> to halt execution.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Here are some variations of \u003Ccode>d()\u003C\u002Fcode> to give you the display you want:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>~d( $var );\u003C\u002Fcode> outputs in plain text format.\u003C\u002Fli>\n\u003Cli>\u003Ccode>+d( $var );\u003C\u002Fcode> disregards depth level limits and outputs everything\u003C\u002Fli>\n\u003Cli>\u003Ccode>!d( $var );\u003C\u002Fcode> shows expanded rich output\u003C\u002Fli>\n\u003Cli>\u003Ccode>-d( $var );\u003C\u002Fcode> attempts to ob_clean() the previous output (dump something inside of HTML)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Profiler\u003C\u002Fh4>\n\u003Cp>Kint even includes a naïve profiler, which can help you analyze which blocks of code take longer than others:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Kint::dump( microtime() ); \u002F\u002F just pass microtime()\nsleep( 1 );\nKint::dump( microtime(), 'after sleep(1)' );\nsleep( 2 );\nddd( microtime(), 'final call, after sleep(2)' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fkint-php-debugger\u002Fscreenshots\u002F\" rel=\"ugc\">screenshot 2\u003C\u002Fa> for what is rendered out in your browser.\u003C\u002Fp>\n\u003Ch3>Admin Bar\u003C\u002Fh3>\n\u003Cp>“KINT ACTIVE” indicator displays in the WordPress admin bar to alert you when the plugin is active.\u003C\u002Fp>\n","Kint is a modern and powerful PHP debugging helper, which requires zero-setup and replaces var_dump(), print_r() and debug_backtrace().",13073,12,"2019-03-11T17:29:00.000Z","5.1.22","5.3",[20,55,21,23,24],"debugger","https:\u002F\u002Fgithub.com\u002FKnowTheCode\u002Fkint-php-debugger","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkint-php-debugger.2.0.2.zip",{"slug":59,"name":60,"version":61,"author":45,"author_profile":46,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":13,"num_ratings":66,"last_updated":67,"tested_up_to":52,"requires_at_least":68,"requires_php":69,"tags":70,"homepage":72,"download_link":73,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"debug-toolkit","Debug Toolkit","1.0.1","\u003Cp>Debug Toolkit makes debugging your code easier and more enjoyable.  It provides you with interactive and helpful tools:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Better PHP error interface from (\u003Ca href=\"http:\u002F\u002Ffilp.github.io\u002Fwhoops\u002F\" rel=\"nofollow ugc\">Whoops\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>Better variable inspection – no need to use \u003Ccode>var_dump\u003C\u002Fcode>, \u003Ccode>print_r\u003C\u002Fcode>, or X-debug\u003C\u002Fli>\n\u003Cli>An interactive way to back trace the program’s execution order\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Better PHP Error Interface from Whoops\u003C\u002Fh3>\n\u003Cp>The built-in PHP error container is basic and not as helpful as it could be.  On top of that, it’s rather ugly. Wouldn’t you agree?\u003C\u002Fp>\n\u003Cp>Whoops gives you a cool interface that is helpful, interactive, and quite nice to look at.  Some features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Provides the error message and links to search Google, DuckDuckGo, and Stack Overflow.\u003C\u002Fli>\n\u003Cli>Shows the actual code where the error occurred.\u003C\u002Fli>\n\u003Cli>Provides an interactive call stack.  Click each and the actual code appears in the viewer panel.\u003C\u002Fli>\n\u003Cli>Environment and details including GET Data, POST Data, Files, Cookie, Session, Server\u002FRequest Data, Environment Variables, and Registered Handlers.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See the tools in action in this video\u003C\u002Fp>\n\u003Cp>\u003Ciframe loading=\"lazy\" title=\"Introducing the Debug Toolkit Plugin for WordPress\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F322351688?dnt=1&app_id=122963\" width=\"750\" height=\"422\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write\">\u003C\u002Fiframe>\u003C\u002Fp>\n\u003Ch3>Better Variable Inspection\u003C\u002Fh3>\n\u003Cp>Though X-debug is powerful, it can be difficult to set up and run.  For that reason, it’s common to dump or print out the variable to browser.  But the built-in display for the PHP \u003Ccode>var_dump\u003C\u002Fcode> and \u003Ccode>print_r\u003C\u002Fcode> is basic.\u003C\u002Fp>\n\u003Cp>This plugin includes both two very popular variable dumper tools:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fsymfony.com\u002Fdoc\u002Fcurrent\u002Fcomponents\u002Fvar_dumper.html\" rel=\"nofollow ugc\">VarDumper from Symfony\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkint-php.github.io\u002Fkint\u002F\" rel=\"nofollow ugc\">Kint – a modern and powerful PHP debugging helper\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>VarDumper provides a simple container that displays where you place it.\u003C\u002Fp>\n\u003Cp>On the other hand, Kint provides a more powerful interface that gives you more information such as printing out the expression that was passed into it, the data type, memory size, and the value.\u003C\u002Fp>\n\u003Cp>To make it even easier, the following utility functions are available for you to use in your code:\u003C\u002Fp>\n\u003Ch4>Available Functions for Inspecting Variable Values\u003C\u002Fh4>\n\u003Cp>Let’s explore the functions that are available for you through this plugin.  We’ll use the variable inspectors to dump \u003Ccode>global $post\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Note: You can pass in any variable or function that returns a value.\u003C\u002Fp>\n\u003Cp>Dumps the given variable(s):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>global $post;\n\n\u002F\u002F VarDumper\nvdump( $post );\n\n\u002F\u002F Kint\ndump( $post );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Dumps the given variable(s) and then exits the program’s execution:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>global $post;\n\n\u002F\u002F VarDumper\nvdump_and_die( $post );\n\n\u002F\u002F Kint\ndump_and_die( $post );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>In addition, there are alias (shorthand) functions available for you if you prefer shorter function names:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>vd()\u003C\u002Fcode> is an alias for \u003Ccode>vdump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>vdd()\u003C\u002Fcode> and \u003Ccode>vdd()\u003C\u002Fcode> are aliases for \u003Ccode>vdump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>d()\u003C\u002Fcode> is an alias for \u003Ccode>dump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>dd()\u003C\u002Fcode> and \u003Ccode>ddd()\u003C\u002Fcode> are aliases for \u003Ccode>dump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Tracing Call Stack\u003C\u002Fh3>\n\u003Cp>When debugging, there are times when you need to see the order in which functions were called that lead to a certain point in the program.  PHP offers a backtrace that traces back the execution order from the point when the function is invoked.\u003C\u002Fp>\n\u003Cp>To make backtracing easier, this plugin provides you with a \u003Ccode>trace()\u003C\u002Fcode> function and combines it with the variable inspect functions.\u003C\u002Fp>\n\u003Cp>For example, if you wanted to trace the call stack to the start of the loop in your theme’s \u003Ccode>functions.php\u003C\u002Fcode> file, you could use this code:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action( 'loop_start', function() {\n    trace();\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Available Trace Functions\u003C\u002Fh4>\n\u003Cp>Place these functions at the point where you want to trace the call stack.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>trace();\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_vdump();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vdump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_dump();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>dump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_vdump_and_die();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vdump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_dump_and_die();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>dump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition, there are alias (shorthand) functions available for you if you prefer shorter function names:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>tracevd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>traced();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>d()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>tracevdd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vdd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>tracedd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>dd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>tracevddd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vddd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>traceddd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>ddd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Admin Bar\u003C\u002Fh3>\n\u003Cp>“DEBUG ACTIVE” indicator displays in the WordPress admin bar to alert you when the plugin is active.\u003C\u002Fp>\n","Code debug made easier and more enjoyable.",20,8785,13,"2019-03-11T15:34:00.000Z","4.9","5.6",[71,20,55,23,24],"backtrace","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-toolkit","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-toolkit.1.0.1.zip",{"slug":75,"name":76,"version":61,"author":77,"author_profile":78,"description":79,"short_description":80,"active_installs":81,"downloaded":82,"rating":13,"num_ratings":83,"last_updated":84,"tested_up_to":85,"requires_at_least":86,"requires_php":18,"tags":87,"homepage":18,"download_link":92,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"laravel-dd","Laravel DD for WordPress","phegman","https:\u002F\u002Fprofiles.wordpress.org\u002Fphegman\u002F","\u003Cp>Use Laravel’s \u003Ca href=\"https:\u002F\u002Flaravel.com\u002Fdocs\u002F5.4\u002Fhelpers#method-dd\" rel=\"nofollow ugc\">\u003Ccode>dd()\u003C\u002Fcode>\u003C\u002Fa> (die dump) function in your WordPress projects. Perfect for debuging custom queries! Laravel’s \u003Ccode>dd()\u003C\u002Fcode> function is built on top of the \u003Ca href=\"http:\u002F\u002Fsymfony.com\u002Fdoc\u002Fcurrent\u002Fcomponents\u002Fvar_dumper.html\" rel=\"nofollow ugc\">Symfony VarDumper component\u003C\u002Fa> \u003Cstrong>Please note in order for this plugin to work correctly WordPress Emojis will be disabled\u003C\u002Fstrong>\u003C\u002Fp>\n","Use Laravel's dd() (die dump) function in your Wordpress projects. Perfect for debuging custom queries!",1000,15070,7,"2018-03-02T22:32:00.000Z","4.8.28","3.0.1",[20,88,89,90,91],"die","dump","laravel","var-dumper","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flaravel-dd.zip",{"slug":94,"name":95,"version":96,"author":97,"author_profile":98,"description":99,"short_description":100,"active_installs":101,"downloaded":102,"rating":13,"num_ratings":103,"last_updated":104,"tested_up_to":105,"requires_at_least":106,"requires_php":18,"tags":107,"homepage":109,"download_link":110,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-dbug","wp-dBug","0.2","vhauri","https:\u002F\u002Fprofiles.wordpress.org\u002Fvhauri\u002F","\u003Cp>This plugin is basically a wrapper for the excellent dBug (http:\u002F\u002Fdbug.ospinto.com) class for PHP debugging, written by Kwaku Otchere..\u003C\u002Fp>\n\u003Cp>Instead of var_dump or echo, you can call wp_dbug( $variable ) to get clear, dynamic debug output of strings, arrays, or objects.\u003C\u002Fp>\n\u003Cp>Thanks to @borkweb, the plugin is now compatible with the WP Debug Bar plugin (https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdebug-bar\u002F) for extra debugging goodness!\u003C\u002Fp>\n","Plugin implements the awesome dBug class created by Kwaku Otchere for use in WordPress plugin debugging",70,6126,2,"2013-01-19T00:07:00.000Z","3.5.2","2.7",[108,20,55,24],"dbug","http:\u002F\u002Fneverblog.net\u002Fwp-dbug","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-dbug.zip",{"slug":112,"name":113,"version":114,"author":115,"author_profile":116,"description":117,"short_description":118,"active_installs":11,"downloaded":119,"rating":13,"num_ratings":14,"last_updated":120,"tested_up_to":105,"requires_at_least":17,"requires_php":18,"tags":121,"homepage":123,"download_link":124,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"pretty-debug","Pretty Debug","1.0","wycks","https:\u002F\u002Fprofiles.wordpress.org\u002Fwycks\u002F","\u003Cp>Make var_dump’s and print_r’s more readable\u003C\u002Fp>\n\u003Cp>Function output references with \u003Ca href=\"http:\u002F\u002Fqueryposts.com\" rel=\"nofollow ugc\">http:\u002F\u002Fqueryposts.com\u003C\u002Fa> API when possible.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Use \u003Ccode>r\u003C\u002Fcode> instead of \u003Ccode>var_dump\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Use \u003Ccode>rt\u003C\u002Fcode> for text mode.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>r($GLOBALS['wp_query']->get_posts());\nrt($GLOBALS['wp_query']->get_posts());\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Notes :\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Probably doesn’t work in ie\u003C\u002Fli>\n\u003Cli>Don’t use this on a production site but you probably already know that\u003C\u002Fli>\n\u003Cli>More usage \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdigitalnature\u002Fphp-ref\" rel=\"nofollow ugc\">https:\u002F\u002Fgithub.com\u002Fdigitalnature\u002Fphp-ref\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>All the work was done by \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdigitalnature\" rel=\"nofollow ugc\">digitalnature\u003C\u002Fa> I just wrapped it into a WordPress plugin and changed the look for inline debugging.\u003C\u002Fp>\n\u003Cp>Please report issues to:  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwycks\u002FWP-Pretty-Debug\" rel=\"nofollow ugc\">https:\u002F\u002Fgithub.com\u002Fwycks\u002FWP-Pretty-Debug\u003C\u002Fa>\u003C\u002Fp>\n","A WordPress plugin that makes var_dump and print_r pretty!",1815,"2013-07-12T00:38:00.000Z",[20,122,24],"debugging","https:\u002F\u002Fgithub.com\u002Fwycks\u002FWP-Pretty-Debug","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpretty-debug.1.0.zip",{"attackSurface":126,"codeSignals":138,"taintFlows":148,"riskAssessment":149,"analyzedAt":160},{"hooks":127,"ajaxHandlers":134,"restRoutes":135,"shortcodes":136,"cronEvents":137,"entryPointCount":28,"unprotectedCount":28},[128],{"type":129,"name":130,"callback":131,"file":132,"line":133},"action","admin_notices","pco_kint_php_error_admin_notice","pco-kint.php",37,[],[],[],[],{"dangerousFunctions":139,"sqlUsage":140,"outputEscaping":142,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":147},[],{"prepared":28,"raw":28,"locations":141},[],{"escaped":28,"rawEcho":14,"locations":143},[144],{"file":132,"line":145,"context":146},34,"raw output",[],[],{"summary":150,"deductions":151},"The static analysis of pco-kint v1.0.10 reveals a plugin with an exceptionally small attack surface and no identified dangerous functions, SQL queries without prepared statements, or file operations. This suggests a foundational level of secure coding practices in these areas. The absence of external HTTP requests and bundled libraries further reduces potential attack vectors. However, a significant concern arises from the total lack of output escaping (0% properly escaped). This means that any dynamic data rendered by the plugin is potentially vulnerable to cross-site scripting (XSS) attacks if user-supplied input is not handled carefully before display.\n\nThe vulnerability history is clean, with no recorded CVEs. This is a positive indicator, but it should be viewed in conjunction with the static analysis findings. The lack of identified vulnerabilities could be due to the limited attack surface or simply a lack of past scrutiny. The absence of nonce and capability checks, while not directly flagged as an issue in the static analysis results (likely due to the zero entry points), would become a critical concern if any entry points were present or introduced in future versions.\n\nOverall, while pco-kint v1.0.10 demonstrates good practices in preventing common vulnerable code patterns and has no historical vulnerabilities, the complete lack of output escaping presents a tangible and serious risk. Future development should prioritize implementing proper output sanitization to mitigate XSS vulnerabilities. The absence of checks for entry points is a weakness that, if entry points are added, would require immediate remediation.",[152,155,158],{"reason":153,"points":154},"0% output escaping",8,{"reason":156,"points":157},"No nonce checks",5,{"reason":159,"points":157},"No capability checks","2026-03-17T01:36:38.049Z",{"wat":162,"direct":167},{"assetPaths":163,"generatorPatterns":164,"scriptPaths":165,"versionParams":166},[],[],[],[],{"cssClasses":168,"htmlComments":169,"htmlAttributes":170,"restEndpoints":171,"jsGlobals":172,"shortcodeOutput":173},[],[],[],[],[],[]]