[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fpyiohSk6uQzT7h5iI3QpfSeByFkj0vbIwI-h-8TzRX4":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":15,"requires_php":15,"tags":16,"homepage":15,"download_link":17,"security_score":18,"vuln_count":13,"unpatched_count":13,"last_vuln_date":19,"fetched_at":20,"vulnerabilities":21,"developer":22,"crawl_stats":19,"alternatives":30,"analysis":31,"fingerprints":50},"a-better-wordpress-importexport","A Better WordPress Import\u002FExport","1.0-alpha","Aaron Brazell","https:\u002F\u002Fprofiles.wordpress.org\u002Ftechnosailor\u002F","\u003Cp>Provides JSON import\u002Fexport for speed and fewer CPU intensive processes\u003C\u002Fp>\n","Provides JSON import\u002Fexport for speed and fewer CPU intensive processes",10,2581,0,"2010-05-10T01:08:00.000Z","",[],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fa-better-wordpress-importexport.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":23,"display_name":7,"profile_url":8,"plugin_count":24,"total_installs":25,"avg_security_score":26,"avg_patch_time_days":27,"trust_score":28,"computed_at":29},"technosailor",4,60,89,4008,71,"2026-04-04T20:20:08.113Z",[],{"attackSurface":32,"codeSignals":38,"taintFlows":45,"riskAssessment":46,"analyzedAt":49},{"hooks":33,"ajaxHandlers":34,"restRoutes":35,"shortcodes":36,"cronEvents":37,"entryPointCount":13,"unprotectedCount":13},[],[],[],[],[],{"dangerousFunctions":39,"sqlUsage":40,"outputEscaping":42,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":44},[],{"prepared":13,"raw":13,"locations":41},[],{"escaped":13,"rawEcho":13,"locations":43},[],[],[],{"summary":47,"deductions":48},"The static analysis of the \"a-better-wordpress-importexport\" plugin v1.0-alpha reveals a seemingly robust security posture.  There are no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in zero attack surface entry points.  Furthermore, the code signals indicate a positive trend with no dangerous functions, file operations, or external HTTP requests.  All SQL queries utilize prepared statements, and all outputs are properly escaped, suggesting good development practices in these areas.  The absence of taint analysis findings further strengthens this impression, with no identified flows involving unsanitized paths.",[],"2026-03-17T00:24:54.959Z",{"wat":51,"direct":60},{"assetPaths":52,"generatorPatterns":55,"scriptPaths":56,"versionParams":57},[53,54],"\u002Fwp-content\u002Fplugins\u002Fa-better-wordpress-importexport\u002Fab_export.css","\u002Fwp-content\u002Fplugins\u002Fa-better-wordpress-importexport\u002Fab_export.js",[],[54],[58,59],"a-better-wordpress-importexport\u002Fab_export.css?ver=","a-better-wordpress-importexport\u002Fab_export.js?ver=",{"cssClasses":61,"htmlComments":62,"htmlAttributes":63,"restEndpoints":64,"jsGlobals":65,"shortcodeOutput":66},[],[],[],[],[],[]]