[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5Ake4srw7W2wYHUy7qEqaCix2zi1xmaEf-5U9LRG8uU":3,"$fyG-AHFushXOc_0yDaQyyK5w8m9mSGE7CSaHMnacGz0Y":202,"$f0UNfiH9_6ZkYewhj5rnwKzWzs_IWun6CABeIaty9o68":207},{"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":24,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":36,"analysis":149,"fingerprints":183},"wp-blade-engine","Blade Engine","1.0.1","Lars Jansen","https:\u002F\u002Fprofiles.wordpress.org\u002Flars-2\u002F","\u003Cp>This plugin adds and loads philo\u002Flaravel-blade to your WordPress installation.\u003Cbr \u002F>\nIt loads two functions, which enable you to use the Blade render engine in your templates which make your themes better readable.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>The plugin adds two functions:\u003Cbr \u002F>\n– render_blade_view (void, echoes the content)\u003Cbr \u002F>\n– get_rendered_blade_view (string)\u003C\u002Fp>\n\u003Cp>Both functions take the same parameters:\u003Cbr \u002F>\n1. view (required, string)\u003Cbr \u002F>\n2. attributes (optional, array)\u003C\u002Fp>\n\u003Cp>When installed, the plugin creates a “views” folder in your theme directory. This is where you put your blade templates (with the .blade.php extension).\u003Cbr \u002F>\nThe “views” folder may contain subfolders.\u003C\u002Fp>\n\u003Ch3>Example\u003C\u002Fh3>\n\u003Cp>wp-contents\u002Fthemes\u002Fyour-theme\u002Fviews\u002Fcomponents\u002Farticle.blade.php:\u003Cbr \u002F>\n    \u003Ccode>blade\u003Cbr \u002F>\n@if($show_text)\u003Cbr \u002F>\n{{ $text }}\u003Cbr \u002F>\n@endif\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>wp-contents\u002Fthemes\u002Fyour-theme\u002Ffunctions.php:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\n\u003C?php\u003Cbr \u002F>\nrender_blade_view('components.article', [\u003Cbr \u002F>\n    'show_text' => true,\u003Cbr \u002F>\n    'text' => 'Hello World!',\u003Cbr \u002F>\n]);\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>When ran on any page, it will output “Hello World!”\u003C\u002Fp>\n\u003Ch3>Blade\u003C\u002Fh3>\n\u003Cp>Blade is a template engine which is mainly used by Laravel. More information here: https:\u002F\u002Flaravel.com\u002Fdocs\u002F5.1\u002Fblade\u003Cbr \u002F>\nThis plugin supports all the directives which are available in Laravel 5.1.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This file is part of Blade Engine.\u003C\u002Fp>\n\u003Cp>Blade Engine is free software: you can redistribute it and\u002For modify it under the terms of the GNU General Public License as published\u003Cbr \u002F>\nby the Free Software Foundation.\u003C\u002Fp>\n\u003Cp>Blade Engine is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of\u003Cbr \u002F>\nMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.\u003C\u002Fp>\n\u003Cp>Get a copy of the GNU General Public License in \u003Ca href=\"http:\u002F\u002Fwww.gnu.org\u002Flicenses\u002F\" rel=\"nofollow ugc\">http:\u002F\u002Fwww.gnu.org\u002Flicenses\u002F\u003C\u002Fa>.\u003C\u002Fp>\n","Adds Blade functionality to your theme",20,1933,0,"2017-08-06T20:32:00.000Z","4.8.28","4.8","",[19,20,21,22,23],"blade","blade-render-engine","engine","laravel","render","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-blade-engine.1.0.1.zip",85,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"lars-2",2,30,84,"2026-05-20T02:52:41.096Z",[37,56,80,100,125],{"slug":19,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":17,"tags":51,"homepage":53,"download_link":54,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":55},"Blade","0.3.7","Mikael Mattsson","https:\u002F\u002Fprofiles.wordpress.org\u002Fkonvent\u002F","\u003Cp>Blade is the template engine for Laravel, a very popular php framework, developed by Taylor Otwell. This plugin brings the same template engine to wordpress.\u003Cbr \u002F>\nUsing a template engine will result in much cleaner template files and quicker development. Normal php can still be used in the template files.\u003Cbr \u002F>\nThe plugin also adds a wordpress specific snippet to blade. Check out the examples for more info.\u003C\u002Fp>\n\u003Ch4>echo\u002Fprint\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>{{$foo}}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Turns into…\n    \u003C\u002Fp>\n\u003Ch4>if()\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>@if(has_post_thumbnail())\n    {{the_post_thumbnail() }}\n@else \n    \u003Cimg src=\"{{bloginfo( 'template_url' )}}\u002Fimages\u002Fthumbnail-default.jpg\" \u002F>\n@endif\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Turns into…\u003C\u002Fp>\n\u003Cp>        \u003Cimg src=\"\u002Fimages\u002Fthumbnail-default.jpg” \u002F>\n    \u003C\u002Fp>\n\u003Ch4>the loop\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>@wpposts\n    \u003Ca href=\"{{the_permalink()}}\">{{the_title()}}\u003C\u002Fa>\u003Cbr>\n@wpempty\n    \u003Cp>404\u003C\u002Fp>\n@wpend\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Turns into…\u003C\u002Fp>\n\u003Cp>        \u003Ca href=\"”>\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>404\u003C\u002Fp>\n\u003Ch4>wordpress query\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>\u003Cul>\n@wpquery(array('post_type' => 'post'))\n    \u003Cli>\u003Ca href=\"{{the_permalink()}}\">{{the_title()}}\u003C\u002Fa>\u003C\u002Fli>\n@wpempty\n    \u003Cli>{{ __('Sorry, no posts matched your criteria.') }}\u003C\u002Fli>\n@wpend\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Turns into….\u003C\u002Fp>\n\u003Cul>\n     ‘post’) ); ?>\u003Cbr \u002F>\n    have_posts() ) : ?>\u003Cbr \u002F>\n        have_posts() ) : $query->the_post(); ?>\u003C\u002Fp>\n\u003Cli>\u003Ca href=\"”>  \u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Advanced Custom Fields\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>\u003Cul>\n    @acfrepeater('images')\n        \u003Cli>{{ get_sub_field( 'image' ) }}\u003C\u002Fli>\n    @acfend\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Turns into…\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cimg src=\"” \u002F>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Including other templates\u003C\u002Fh4>\n\u003Cp>To include a file with blade use:\u003Cbr \u002F>\n    @include(‘header’)\u003Cbr \u002F>\nNote that you should not type “.php”. Files included with functions, e.g. the_header(), will not be compiled by Blade, however the php code in the file is still executed.\u003C\u002Fp>\n\u003Ch4>Layouts\u003C\u002Fh4>\n\u003Cp>master.php:\u003C\u002Fp>\n\u003Cp>            @yield(‘content’)\u003C\u002Fp>\n\u003Cp>page.php:\u003Cbr \u002F>\n    @layout(‘master’)\u003C\u002Fp>\n\u003Cpre>\u003Ccode>@section('content')\n    \u003Cp>Lorem ipsum\u003C\u002Fp>\n@endsection\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>See the \u003Ca href=\"http:\u002F\u002Fthree.laravel.com\u002Fdocs\u002Fviews\u002Ftemplating\" title=\"Laravel 3 Templating\" rel=\"nofollow ugc\">Blade documentation\u003C\u002Fa> for more info.\u003C\u002Fp>\n\u003Cp>Contribute on github: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMikaelMattsson\u002Fblade\" rel=\"nofollow ugc\">github.com\u002FMikaelMattsson\u002Fblade\u003C\u002Fa>\u003C\u002Fp>\n","Brings Laravel's great template engine, Blade, to Wordpress. Just install and start using blade in your theme.",200,7353,80,7,"2015-12-01T06:26:00.000Z","3.9.40","3.0.0",[19,21,22,52],"template","https:\u002F\u002Fgithub.com\u002FMikaelMattsson\u002Fblade","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblade.0.3.7.zip","2026-04-16T10:56:18.058Z",{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":66,"num_ratings":67,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":17,"tags":71,"homepage":77,"download_link":78,"security_score":34,"vuln_count":32,"unpatched_count":13,"last_vuln_date":79,"fetched_at":55},"async-javascript","Async JavaScript","2.21.08.31","David Clough","https:\u002F\u002Fprofiles.wordpress.org\u002Fcloughit\u002F","\u003Cp>Eliminate Render-blocking Javascript in above-the-fold content with Async Javascript.\u003C\u002Fp>\n\u003Cp>Render-blocking Javascript prevents above-the-fold content on your page from being rendered until the javascript has finished loading. This can impact on your page speed and ultimately your ranking within search engines. It can also impact your user’s experience.\u003C\u002Fp>\n\u003Cp>Async JavaScript gives you full control of which scripts to add an ‘async’ or ‘defer’ attribute to or to exclude to help increase the performance of your WordPress website.\u003C\u002Fp>\n","Async Javascript lets you add 'async' or 'defer' attribute to scripts to exclude to help increase the performance of your WordPres …",70000,2050702,94,102,"2023-06-22T08:00:00.000Z","6.2.9","4.6",[72,73,74,75,76],"async","javascript","pagespeed","performance","render-blocking","https:\u002F\u002Fautoptimize.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fasync-javascript.2.21.08.31.zip","2021-06-13 00:00:00",{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":64,"downloaded":88,"rating":89,"num_ratings":90,"last_updated":91,"tested_up_to":92,"requires_at_least":93,"requires_php":94,"tags":95,"homepage":98,"download_link":99,"security_score":89,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":55},"speculation-rules","Speculative Loading","1.6.0","WordPress Performance Team","https:\u002F\u002Fprofiles.wordpress.org\u002Fperformanceteam\u002F","\u003Cp>This plugin adds support for the \u003Ca href=\"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FSpeculation_Rules_API\" rel=\"nofollow ugc\">Speculation Rules API\u003C\u002Fa>, which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was \u003Ca href=\"https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2025\u002F03\u002F06\u002Fspeculative-loading-in-6-8\u002F\" rel=\"nofollow ugc\">merged into WordPress 6.8\u003C\u002Fa>, but it only prefetches with conservative eagerness by default. In contrast, this plugin defaults to prerendering with moderate eagerness (i.e. when interacting with a link), and it provides a user interface to customize the mode and eagerness via the “Speculative Loading” section on the \u003Cem>Settings > Reading\u003C\u002Fem> admin screen.\u003C\u002Fp>\n\u003Cp>By default, speculative loading is only enabled for logged-out users, since unauthenticated pages are typically only eligible for caching and so more efficient to prefetch\u002Fprerender. This means that sites with frequent logged-in users on the frontend—such as e-commerce, forums, or membership sites—will not benefit from the feature. If your server can handle the additional load (for example, with persistent object caching), you can opt in to enable speculative loading for all logged-in users or for administrators only. This setting exclusively affects frontend pages; admin screens are always excluded.\u003C\u002Fp>\n\u003Cp>A filter can be used to exclude certain URL paths from being eligible for prefetching and prerendering (see FAQ section). Alternatively, you can add the \u003Ccode>no-prerender\u003C\u002Fcode> CSS class to any link (\u003Ccode>\u003Ca>\u003C\u002Fcode> tag) that should not be prerendered. See FAQ for more information.\u003C\u002Fp>\n\u003Ch4>Browser support\u003C\u002Fh4>\n\u003Cp>The Speculation Rules API is a new web API, and the functionality used by the plugin is supported in Chromium-based browsers such as Chrome, Edge, or Opera using version 121 or above. Other browsers such as Safari and Firefox will ignore the functionality with no ill effects; they will simply not benefit from the speculative loading. Note that certain browser extensions may disable preloading by default.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcaniuse.com\u002Fmdn-html_elements_script_type_speculationrules\" rel=\"nofollow ugc\">Browser support for the Speculation Rules API in general\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Fweb-platform\u002Fprerender-pages\" rel=\"nofollow ugc\">Information on document rules syntax support used by the plugin\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>This plugin was formerly known as Speculation Rules.\u003C\u002Fem>\u003C\u002Fp>\n","Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction.",411087,100,18,"2025-12-02T22:34:00.000Z","6.9.4","6.6","7.2",[73,75,96,97,81],"prefetch","prerender","https:\u002F\u002Fgithub.com\u002FWordPress\u002Fperformance\u002Ftree\u002Ftrunk\u002Fplugins\u002Fspeculation-rules","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fspeculation-rules.1.6.0.zip",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":108,"downloaded":109,"rating":110,"num_ratings":111,"last_updated":112,"tested_up_to":92,"requires_at_least":113,"requires_php":114,"tags":115,"homepage":121,"download_link":122,"security_score":123,"vuln_count":32,"unpatched_count":13,"last_vuln_date":124,"fetched_at":55},"boldgrid-easy-seo","BoldGrid Easy SEO – Simple and Effective SEO","1.6.17","BoldGrid","https:\u002F\u002Fprofiles.wordpress.org\u002Fboldgrid\u002F","\u003Ch4>Automatically Optimize Your SEO with BoldGrid Easy SEO and Rank Higher in the Search Engines\u003C\u002Fh4>\n\u003Cp>BoldGrid Easy SEO will help you create better content and rank higher in the search engines. It analyzes your page content in real-time and makes recommendations that will help you maintain best SEO practices. Simply set a target keyword or phrase and the BoldGrid Easy SEO dashboard will automatically give you easy-to-follow suggestions on improving your on-page SEO. Regardless of your SEO skill level or knowledge, BoldGrid Easy SEO provides simple, yet powerful tools for website search engine optimization. Get automatic assistance with:\u003C\u002Fp>\n\u003Ch4>Optimal Keyword Density\u003C\u002Fh4>\n\u003Cp>BoldGrid Easy SEO will analyze your content in real-time to ensure your targeted keyword appears at the optimal frequency, as well as in the right places on the page.\u003C\u002Fp>\n\u003Ch4>Page Titles and Descriptions\u003C\u002Fh4>\n\u003Cp>Control and optimize how your pages appear in Google rankings pages with the title and description editor. BoldGrid Easy SEO will also make sure your target keyword is included.\u003C\u002Fp>\n\u003Ch4>Header Tags and Content\u003C\u002Fh4>\n\u003Cp>BoldGrid Easy SEO will automatically analyze your header tags and give you recommendations on their proper usage, as well as assisting you with including relevant content.\u003C\u002Fp>\n\u003Ch4>Image Alt Tags\u003C\u002Fh4>\n\u003Cp>BoldGrid Easy SEO automatically checks your images for alt tags to help you identify areas for SEO improvement.\u003C\u002Fp>\n\u003Ch4>Content Length\u003C\u002Fh4>\n\u003Cp>Keyword rich content is a prime factor when search engines determine rankings. BoldGrid Easy SEO will assist you in writing better content by tracking your progress and alerting you when you’ve reached the sweet spot.\u003C\u002Fp>\n\u003Ch4>Search Engine Indexing\u003C\u002Fh4>\n\u003Cp>Allow (or disallow) search engines from indexing pages with a single click.\u003C\u002Fp>\n\u003Ch4>Follow\u002FNo Follow Links\u003C\u002Fh4>\n\u003Cp>Choose whether your links are visible to search engines and count toward your SEO, or hide them if necessary.\u003C\u002Fp>\n\u003Ch4>Canonical URLs\u003C\u002Fh4>\n\u003Cp>Avoid duplicate content penalties by indicating a canonical URL where applicable.\u003C\u002Fp>\n","Easy SEO helps you easily create keyword rich content and rank higher in the search engines.",50000,826800,60,3,"2025-12-01T21:07:00.000Z","4.4","5.3",[116,117,118,119,120],"boldgrid","content-analysis","readability","search-engine-optimization","seo","https:\u002F\u002Fwww.boldgrid.com\u002Fboldgrid-seo\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fboldgrid-easy-seo.1.6.17.zip",99,"2024-04-05 00:00:00",{"slug":126,"name":127,"version":128,"author":129,"author_profile":130,"description":131,"short_description":132,"active_installs":133,"downloaded":134,"rating":135,"num_ratings":136,"last_updated":137,"tested_up_to":138,"requires_at_least":139,"requires_php":140,"tags":141,"homepage":145,"download_link":146,"security_score":147,"vuln_count":32,"unpatched_count":13,"last_vuln_date":148,"fetched_at":55},"timber-library","Timber","1.23.4","jarednova","https:\u002F\u002Fprofiles.wordpress.org\u002Fjarednova\u002F","\u003Cp>With the upcoming release of Timber 2.0, we will not release a 2.0 version and beyond as a plugin, but only as a Composer package. We advise everyone to switch to the Composer based install as soon as possible.\u003Cbr \u002F>\nYou will find an extensive list with guides and the reasons why we are not going to release Timber 2.0 as a plugin anymore.\u003C\u002Fp>\n\u003Ch3>Switching to the Composer based version\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Announcement: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftimber\u002Ftimber\u002Fdiscussions\u002F2804\" rel=\"nofollow ugc\">Dropping support for the plugin version of Timber\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Guide: \u003Ca href=\"https:\u002F\u002Ftimber.github.io\u002Fdocs\u002Fv1\u002Fgetting-started\u002Fswitch-to-composer\u002F\" rel=\"nofollow ugc\">How do I switch over from the plugin version to the Composer based version of Timber?\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Backstory: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftimber\u002Ftimber\u002Fpull\u002F2005\" rel=\"nofollow ugc\">Why we are dropping support for the plugin in the first place\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>GitHub issue: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftimber\u002Ftimber\u002Fissues\u002F2741\" rel=\"nofollow ugc\">Roadmap for Timber 2.0\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Timber helps you create fully-customized WordPress themes faster with more sustainable code. With Timber, you write your HTML using the \u003Ca href=\"http:\u002F\u002Ftwig.sensiolabs.org\u002F\" rel=\"nofollow ugc\">Twig Template Engine\u003C\u002Fa> separate from your PHP files. This cleans up your theme code so, for example, your PHP file can focus on being the data\u002Flogic, while your Twig file can focus 100% on the HTML and display.\u003C\u002Fp>\n\u003Cp>Once Timber is installed and activated in your plugin directory, it gives any WordPress theme the ability to take advantage of the power of Twig and other Timber features.\u003C\u002Fp>\n\u003Ch3>Want to learn more?\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ca href=\"http:\u002F\u002Fupstatement.com\u002Ftimber\" rel=\"nofollow ugc\">Project Page\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftimber\u002Ftimber\u002F\" rel=\"nofollow ugc\">Timber on GitHub\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Looking for Documentation?\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftimber.github.io\u002Fdocs\u002F\" rel=\"nofollow ugc\">Timber Documentation\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Ftwig.sensiolabs.org\u002Fdoc\u002Ftemplates.html\" rel=\"nofollow ugc\">Twig Reference (from SensioLabs)\u003C\u002Fa>\u003Cbr \u002F>\n\u003Cem>Twig is the template language powering Timber; if you need a little background on what a template language is, \u003Ca href=\"http:\u002F\u002Ftwig.sensiolabs.org\u002F\" rel=\"nofollow ugc\">Twig’s homepage has an overview\u003C\u002Fa>\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Ftimber.github.io\u002Fdocs\u002Fgetting-started\u002Fvideo-tutorials\u002F\" rel=\"nofollow ugc\">Video Tutorials\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftimber.github.io\u002Fdocs\u002Fgetting-started\u002F\" rel=\"nofollow ugc\">Overview \u002F Getting Started Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Need support?\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fstackoverflow.com\u002Fquestions\u002Ftagged\u002Ftimber\" rel=\"nofollow ugc\">StackOverflow\u003C\u002Fa> is for usage questions and troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftimber\u002Ftimber\u002Fissues\" rel=\"nofollow ugc\">GitHub issues\u003C\u002Fa> are for reporting bugs and errors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>Please post on \u003Ca href=\"http:\u002F\u002Fstackoverflow.com\u002Fquestions\u002Ftagged\u002Ftimber\" rel=\"nofollow ugc\">StackOverflow under the “Timber” tag\u003C\u002Fa>. Please use GitHub issues only for specific bugs, feature requests and other types of issues.\u003C\u002Fp>\n","Helps you create themes faster with sustainable code. With Timber, you write HTML using Twig Templates http:\u002F\u002Fwww.upstatement.com\u002Ftimber\u002F",20000,1464925,98,71,"2025-05-31T20:07:00.000Z","6.8.5","5.3.0","7.2.5",[142,143,144],"template-engine","templates","twig","https:\u002F\u002Fupstatement.com\u002Ftimber","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftimber-library.1.23.4.zip",97,"2025-07-24 00:00:00",{"attackSurface":150,"codeSignals":156,"taintFlows":168,"riskAssessment":169,"analyzedAt":182},{"hooks":151,"ajaxHandlers":152,"restRoutes":153,"shortcodes":154,"cronEvents":155,"entryPointCount":13,"unprotectedCount":13},[],[],[],[],[],{"dangerousFunctions":157,"sqlUsage":158,"outputEscaping":160,"fileOperations":32,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":167},[],{"prepared":13,"raw":13,"locations":159},[],{"escaped":13,"rawEcho":161,"locations":162},1,[163],{"file":164,"line":165,"context":166},"wp-blade-engine.php",32,"raw output",[],[],{"summary":170,"deductions":171},"The \"wp-blade-engine\" v1.0.1 plugin exhibits a generally positive security posture based on the provided static analysis. There are no identified dangerous functions, external HTTP requests, or raw SQL queries, indicating good practices in these areas. The absence of known vulnerabilities in its history is also a strong indicator of a well-maintained codebase. \n\nHowever, there are notable concerns. The analysis reveals that 100% of the single output detected is not properly escaped, presenting a significant risk of Cross-Site Scripting (XSS) vulnerabilities. Furthermore, the plugin performs file operations, and without proper validation or sanitization, these could potentially lead to insecure file handling. The lack of nonce and capability checks across all entry points, though the attack surface is currently zero, means that if any new entry points are introduced in the future, they would be vulnerable to unauthorized actions and CSRF attacks.\n\nIn conclusion, while the plugin has a clean vulnerability history and avoids several common pitfalls, the unescaped output is a critical flaw that needs immediate attention. The file operations also warrant careful review. Addressing these specific weaknesses will significantly improve the plugin's overall security.",[172,175,178,180],{"reason":173,"points":174},"Unescaped output detected",8,{"reason":176,"points":177},"File operations present without other checks",5,{"reason":179,"points":177},"Missing nonce checks on entry points",{"reason":181,"points":177},"Missing capability checks on entry points","2026-03-16T23:06:01.519Z",{"wat":184,"direct":193},{"assetPaths":185,"generatorPatterns":188,"scriptPaths":189,"versionParams":190},[186,187],"\u002Fwp-content\u002Fplugins\u002Fwp-blade-engine\u002Fresources\u002Fcss\u002Fapp.css","\u002Fwp-content\u002Fplugins\u002Fwp-blade-engine\u002Fresources\u002Fjs\u002Fapp.js",[],[187],[191,192],"wp-blade-engine\u002Fresources\u002Fcss\u002Fapp.css?ver=","wp-blade-engine\u002Fresources\u002Fjs\u002Fapp.js?ver=",{"cssClasses":194,"htmlComments":195,"htmlAttributes":196,"restEndpoints":197,"jsGlobals":198,"shortcodeOutput":199},[],[],[],[],[],[200,201],"render_blade_view","get_rendered_blade_view",{"error":203,"url":204,"statusCode":205,"statusMessage":206,"message":206},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fwp-blade-engine\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":32,"versions":208},[209,215],{"version":6,"download_url":24,"svn_tag_url":210,"released_at":26,"has_diff":211,"diff_files_changed":212,"diff_lines":26,"trac_diff_url":213,"vulnerabilities":214,"is_current":203},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fwp-blade-engine\u002Ftags\u002F1.0.1\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fwp-blade-engine%2Ftags%2F1.0.0&new_path=%2Fwp-blade-engine%2Ftags%2F1.0.1",[],{"version":216,"download_url":217,"svn_tag_url":218,"released_at":26,"has_diff":211,"diff_files_changed":219,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":220,"is_current":211},"1.0.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-blade-engine.1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fwp-blade-engine\u002Ftags\u002F1.0.0\u002F",[],[]]