[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fE-tn8LG4nwIKyRhWt0BrF4HqSsBh-kv2_my_twIW4-I":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":17,"download_link":19,"security_score":20,"vuln_count":13,"unpatched_count":13,"last_vuln_date":21,"fetched_at":22,"vulnerabilities":23,"developer":24,"crawl_stats":21,"alternatives":32,"analysis":33,"fingerprints":68},"use-innodb","Use InnoDB","1.0.2","WPChef","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpchefgadget\u002F","\u003Cp>This plugin changes the storage engine of the options table from MyISAM to InnoDB. Please take note that if you have a relatively fresh WordPress installation, the options table might already be the InnoDB type. In this case the plugin will not be of any help, but will not cause any issues either.\u003C\u002Fp>\n\u003Cp>The InnoDB storage engine locks tables (when needed) on a single row level, while MyISAM does this on the entire table level, this is less effective and leads to WordPress slow-ness when working with highly loaded sites or large options table.\u003C\u002Fp>\n\u003Cp>The plugin starts working right after activation and doesn’t have any settings.\u003C\u002Fp>\n","Increases performance by changing the storage engine of the options table from MyISAM to InnoDB.",200,2900,0,"2020-04-29T12:56:00.000Z","5.4.19","4.2","",[],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fuse-innodb.1.0.2.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":25,"display_name":7,"profile_url":8,"plugin_count":26,"total_installs":27,"avg_security_score":28,"avg_patch_time_days":29,"trust_score":30,"computed_at":31},"wpchefgadget",3,2003200,89,643,71,"2026-04-04T13:43:04.579Z",[],{"attackSurface":34,"codeSignals":40,"taintFlows":55,"riskAssessment":56,"analyzedAt":67},{"hooks":35,"ajaxHandlers":36,"restRoutes":37,"shortcodes":38,"cronEvents":39,"entryPointCount":13,"unprotectedCount":13},[],[],[],[],[],{"dangerousFunctions":41,"sqlUsage":42,"outputEscaping":52,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":54},[],{"prepared":13,"raw":43,"locations":44},2,[45,49],{"file":46,"line":47,"context":48},"innodb.php",39,"$wpdb->get_row() with variable interpolation",{"file":46,"line":50,"context":51},45,"$wpdb->query() with variable interpolation",{"escaped":13,"rawEcho":13,"locations":53},[],[],[],{"summary":57,"deductions":58},"The 'use-innodb' v1.0.2 plugin presents a strong security posture based on the provided static analysis.  The absence of any identified attack surface entry points (AJAX handlers, REST API routes, shortcodes, cron events) suggests a minimal footprint, which is generally a positive security trait. Furthermore, the code signals indicate good practices in output escaping, with 100% of outputs being properly escaped, and no dangerous functions, file operations, or external HTTP requests were detected. The lack of any reported vulnerabilities or CVEs historically is also a very reassuring indicator of the plugin's security track record.",[59,62,65],{"reason":60,"points":61},"Raw SQL queries without prepared statements",10,{"reason":63,"points":64},"No nonce checks implemented",5,{"reason":66,"points":64},"No capability checks implemented","2026-03-16T20:16:48.532Z",{"wat":69,"direct":74},{"assetPaths":70,"generatorPatterns":71,"scriptPaths":72,"versionParams":73},[],[],[],[],{"cssClasses":75,"htmlComments":76,"htmlAttributes":77,"restEndpoints":78,"jsGlobals":79,"shortcodeOutput":80},[],[],[],[],[],[]]