[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fu5PTy2MXisw7YZegkb3SZJZNvTkVM2FpRZbu8HKEhzY":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":20,"download_link":21,"security_score":22,"vuln_count":23,"unpatched_count":23,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":32,"analysis":33,"fingerprints":67},"query-loop-exclude-posts","Query Loop Exclude Posts","1.1.0","ColinD","https:\u002F\u002Fprofiles.wordpress.org\u002Fcolind\u002F","\u003Cp>Extends the Query Loop Block to allow excluding specific posts.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Provides controls in the Query Loop Block Select specific posts by title.\u003C\u002Fli>\n\u003Cli>Provides a toggle to exclude the current post.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Works with whichever post type is set for the query loop Block (Post, Page, etc)\u003C\u002Fp>\n\u003Cp>“Exclude Current Post” is helpful for “related posts” patterns often used on a single\u003Cbr \u002F>\npost template. Using this option on the query loop block will let it pull in posts but\u003Cbr \u002F>\nnot the single post currently being viewed.\u003C\u002Fp>\n\u003Ch3>Development and Support\u003C\u002Fh3>\n\u003Cp>wp\u003Cbr \u002F>\nThis plugin is developed on Github. You can find the uncompressed source javascript and\u003Cbr \u002F>\nsubmit issues and pull requests there:\u003Cbr \u002F>\nhttps:\u002F\u002Fgithub.com\u002Fcolinduwe\u002Fexclude-posts\u003C\u002Fp>\n\u003Cp>If you’ve checked out the full source code either from my repo or your own fork you’ll\u003Cbr \u002F>\nwant to do the following in your terminal:\u003Cbr \u002F>\n1. Navigate within this plugin’s directory.\u003Cbr \u002F>\n2. Install the development dependencies by running ‘npm install’\u003Cbr \u002F>\n3. Work on the plugin code by running ‘npm start’\u003Cbr \u002F>\n4. Complete your work by building for production by running ‘npm run build’\u003C\u002Fp>\n","Extends the Query Loop Block to allow excluding specific posts.",100,1170,1,"2025-01-20T18:43:00.000Z","6.7.5","6.6","8.0",[19],"query-loop-block","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-loop-exclude-posts.1.1.0.zip",92,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":13,"total_installs":11,"avg_security_score":22,"avg_patch_time_days":29,"trust_score":30,"computed_at":31},"colind",30,88,"2026-04-04T20:16:24.250Z",[],{"attackSurface":34,"codeSignals":55,"taintFlows":62,"riskAssessment":63,"analyzedAt":66},{"hooks":35,"ajaxHandlers":51,"restRoutes":52,"shortcodes":53,"cronEvents":54,"entryPointCount":23,"unprotectedCount":23},[36,41,46],{"type":37,"name":38,"callback":39,"file":40,"line":29},"action","enqueue_block_editor_assets","qlep__enqueue_block_editor_assets","query-loop-exclude-posts.php",{"type":42,"name":43,"callback":44,"file":40,"line":45},"filter","query_loop_block_query_vars","closure",37,{"type":42,"name":47,"callback":48,"priority":49,"file":40,"line":50},"pre_render_block","qlep__pre_render_block",10,58,[],[],[],[],{"dangerousFunctions":56,"sqlUsage":57,"outputEscaping":59,"fileOperations":23,"externalRequests":23,"nonceChecks":23,"capabilityChecks":23,"bundledLibraries":61},[],{"prepared":23,"raw":23,"locations":58},[],{"escaped":23,"rawEcho":23,"locations":60},[],[],[],{"summary":64,"deductions":65},"The \"query-loop-exclude-posts\" plugin v1.1.0 exhibits a strong security posture based on the provided static analysis. The absence of any detected dangerous functions, raw SQL queries, unescaped output, file operations, external HTTP requests, or unsanitized taint flows is highly commendable. Furthermore, the plugin has no recorded history of vulnerabilities, which suggests a consistent commitment to security or simply fortunate lack of discovered issues. The attack surface is also zero, indicating no direct entry points like AJAX handlers, REST API routes, or shortcodes that could be exploited without proper authentication or authorization.",[],"2026-03-16T21:03:35.941Z",{"wat":68,"direct":75},{"assetPaths":69,"generatorPatterns":71,"scriptPaths":72,"versionParams":73},[70],"\u002Fwp-content\u002Fplugins\u002Fquery-loop-exclude-posts\u002Fbuild\u002Findex.js",[],[70],[74],"query-loop-exclude-posts\u002Fbuild\u002Findex.js?ver=",{"cssClasses":76,"htmlComments":77,"htmlAttributes":78,"restEndpoints":79,"jsGlobals":80,"shortcodeOutput":81},[],[],[],[],[],[]]