[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fjx5YLwpJcgUB9mElEYSNAU4JcEzK9P8ln_XFuB-8rIg":3,"$fuMsT0cRXHNWwp44C2i4BioPcs3eUzyy7dXbOQsD989w":188,"$f5s7-SwzB1HLv4crmZ3_fXLsukAm1MmWO5VQaFO7STSY":193},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":11,"rating":11,"num_ratings":11,"last_updated":12,"tested_up_to":13,"requires_at_least":14,"requires_php":15,"tags":16,"homepage":21,"download_link":22,"security_score":23,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25,"discovery_status":26,"vulnerabilities":27,"developer":28,"crawl_stats":24,"alternatives":35,"analysis":137,"fingerprints":171},"glotcore-history-limiter","GlotCore History Limiter","1.0","meloniq","https:\u002F\u002Fprofiles.wordpress.org\u002Fmeloniq\u002F","\u003Cp>Controls and optimizes translation history in \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fglotpress\u002F\" rel=\"ugc\">GlotPress\u003C\u002Fa> by enforcing limits on \u003Ccode>waiting\u003C\u002Fcode> and \u003Ccode>old\u003C\u002Fcode> entries per string,\u003Cbr \u002F>\nreducing unnecessary revisions and keeping the database lean and efficient.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>It limits the number of \u003Ccode>waiting\u003C\u002Fcode> translations.\u003Cbr \u002F>\nAny \u003Ccode>waiting\u003C\u002Fcode> translations above the limit are set to \u003Ccode>old\u003C\u002Fcode> status and are no longer shown in the waiting translations list.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>It limits the number of \u003Ccode>old\u003C\u002Fcode> translations.\u003Cbr \u002F>\nAny \u003Ccode>old\u003C\u002Fcode> translations above the limit are permanently deleted from the database.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>How the limit works\u003C\u002Fh3>\n\u003Cp>Assume the limit is set to \u003Cstrong>2 translations per string\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch3>1. Single user behavior\u003C\u002Fh3>\n\u003Cp>When a single user submits multiple translations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The \u003Cstrong>latest translation\u003C\u002Fstrong> is always marked as \u003Ccode>waiting\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>The previous \u003Ccode>waiting\u003C\u002Fcode> translation becomes \u003Ccode>old\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>If the number of \u003Ccode>old\u003C\u002Fcode> translations exceeds the limit:\n\u003Cul>\n\u003Cli>The \u003Cstrong>oldest \u003Ccode>old\u003C\u002Fcode> translation is deleted\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Result:\u003C\u002Fstrong>\u003Cbr \u002F>\n– \u003Ccode>1 waiting\u003C\u002Fcode> translation (latest)\u003Cbr \u002F>\n– Up to \u003Ccode>2 old\u003C\u002Fcode> translations (limited)\u003C\u002Fp>\n\u003Ch3>2. Multiple users\u003C\u002Fh3>\n\u003Cp>When multiple users submit translations for the same string:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Each user can have \u003Cstrong>one \u003Ccode>waiting\u003C\u002Fcode> translation\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\n\u003Cp>A new submission:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Replaces that user’s previous \u003Ccode>waiting\u003C\u002Fcode> (which becomes \u003Ccode>old\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Does \u003Cstrong>affect other users \u003Ccode>waiting\u003C\u002Fcode> translations\u003C\u002Fstrong> if the total number of \u003Ccode>waiting\u003C\u002Fcode> translations exceeds the limit\u003C\u002Fli>\n\u003Cli>The \u003Cstrong>oldest \u003Ccode>waiting\u003C\u002Fcode> translation\u003C\u002Fstrong> over the limit (regardless of user) becomes \u003Ccode>old\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>All \u003Ccode>old\u003C\u002Fcode> translations are shared (counted globally per string)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>All \u003Ccode>waiting\u003C\u002Fcode> translations are shared (counted globally per string)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Configuration\u003C\u002Fh4>\n\u003Cp>Once installed, GlotCore History Limiter is ready to use. The default limit is set to 3 history entries per string.\u003C\u002Fp>\n\u003Cp>You can change this limit by defining the following constant in your \u003Ccode>wp-config.php\u003C\u002Fcode> file:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\ndefine( 'GLOTCORE_HISTORY_LIMIT', 3 ); \u002F\u002F Change 3 to your desired limit\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>You can also modify the limit by hooking into the \u003Ccode>glotcore_history_limit\u003C\u002Fcode> filter in your theme or plugin:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'glotcore_history_limit', function( $limit ) {\u003Cbr \u002F>\n    return 3; \u002F\u002F Change 3 to your desired limit\u003Cbr \u002F>\n} );\u003C\u002Fcode>\u003C\u002Fp>\n","Limits and manages translation history in GlotPress by controlling the number of waiting and old entries per string to prevent database bloat.",0,"2026-04-15T13:02:00.000Z","6.9.4","4.9","7.4",[17,18,19,20],"glotpress","history","limit","revisions","https:\u002F\u002Fblog.meloniq.net\u002Fgp-history-limiter\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fglotcore-history-limiter.1.0.zip",100,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":31,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},16,710,98,1,99,"2026-05-20T00:03:23.174Z",[36,57,83,99,119],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":23,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":54,"download_link":55,"security_score":56,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"limit-revisions","Limit Revisions","1.0.0","Carlos Martínez Romero","https:\u002F\u002Fprofiles.wordpress.org\u002Fcarlosmr96\u002F","\u003Cp>“Limit Revisions” is a small plugin that allows you to select limit of revisions that WordPress stores in the database. You can select the limit at the bottom of Settings > General. This plugin wont work if the value is already defined elsewhere to avoid errors.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Allows to select limit of revisions that WordPress stores in the database.\u003C\u002Fli>\n\u003Cli>Automatically Delete oldes revision after the limit is reached\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin adds a new setting in the last position of Settings > General, this option will allow you to select limit of revisions that WordPress s …",1000,6658,5,"2023-02-23T20:51:00.000Z","6.1.10","4.0","5.2.4",[52,19,53,20],"content","revision","https:\u002F\u002Fcarlosmr.com\u002Fplugin\u002Flimitar-las-revisiones-en-wordpress\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flimit-revisions.zip",85,{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":65,"downloaded":66,"rating":67,"num_ratings":68,"last_updated":69,"tested_up_to":70,"requires_at_least":71,"requires_php":72,"tags":73,"homepage":79,"download_link":80,"security_score":81,"vuln_count":32,"unpatched_count":32,"last_vuln_date":82,"fetched_at":25},"wp-revisions-manager","WP Revisions Manager","1.0.2","P Roy","https:\u002F\u002Fprofiles.wordpress.org\u002Fraviry\u002F","\u003Cp>It helps you keep a clean database by removing unnecessary posts revisions. It lets you delete specific posts revisions.\u003Cbr \u002F>\nPerfectly integrated in the WordPress back-end, and uses wordpress core functions to safely delete revisions.\u003Cbr \u002F>\nYou can also limit the number of revisions to be stored.\u003C\u002Fp>\n\u003Ch4>How does it work?\u003C\u002Fh4>\n\u003Cp>The plugin adds a discreet link next to the default revisions counter (see screen-shots section).\u003Cbr \u002F>\nWhen you click on it, it will purge the appropriate post revisions via AJAX.\u003Cbr \u002F>\nIt also add a new bulk action option in the post\u002Fpage row view to let you purge revisions of multiple posts at once.\u003C\u002Fp>\n\u003Cp>NOTE: Works only for the post_types that supports ‘revisions’\u003C\u002Fp>\n","WP Revisions Manager let you purge (delete) its revisions via AJAX. There is also a Bulk action in the post lists. You can also limit the number of re …",700,5959,74,3,"2020-09-11T10:46:00.000Z","5.4.19","4.5","",[74,75,76,77,78],"revision-manager","revisions-control","wp-revision-manager","wp-revisions-control","wp-revisions-limit","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-revisions-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-revisions-manager.zip",64,"2024-11-28 00:00:00",{"slug":84,"name":85,"version":86,"author":87,"author_profile":88,"description":89,"short_description":90,"active_installs":23,"downloaded":91,"rating":23,"num_ratings":68,"last_updated":92,"tested_up_to":13,"requires_at_least":14,"requires_php":15,"tags":93,"homepage":97,"download_link":98,"security_score":23,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"time-based-revisions","Time-based Revision Cleanup","1.1.4","Michael Sablone","https:\u002F\u002Fprofiles.wordpress.org\u002Fmichaelsablone\u002F","\u003Cp>Optimize your website’s performance and streamline your editing workflow with the Time-based Revision Cleanup plugin for WordPress. Our plugin offers a sophisticated solution to the limitations of the default number-based revision system, which can quickly become inadequate for active sites. Instead of restricting revisions to a set count, our plugin allows you to specify a timeframe for keeping revisions, such as 30, 60, or 365 days, ensuring that your database retains only what’s necessary without losing the essential edit history of your posts.\u003C\u002Fp>\n\u003Cp>In addition, our plugin enhances the admin dashboard with an analytics feature to generate visual representations of revision history data.\u003C\u002Fp>\n\u003Ch3>Key Features:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Intelligent Age-Based Management\u003C\u002Fstrong>: Preserve your site’s history by automatically deleting revisions past a certain age, keeping only the recent and relevant changes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Seamless On-Save Cleanup\u003C\u002Fstrong>: The plugin intuitively removes outdated revisions upon saving posts, based on the age criteria you’ve set, without disrupting the creative process.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Optional Automated Cleanup\u003C\u002Fstrong>: Enable the optional CRON job to perform regular, site-wide revision cleanups at intervals you control, maintaining optimal database health with no manual effort.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Dashboard Analytics\u003C\u002Fstrong>: Visualize your site’s revision cleanup activity with an integrated chart, powered by Google’s Chart API.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Fully Customizable\u003C\u002Fstrong>: Configure the plugin’s settings to fit the unique demands of your site, including save timeout, CRON frequency, and the maximum number of revisions to process.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>By focusing on time rather than revision count, our plugin addresses the core flaw in the default system, ensuring that a busy day of editing won’t result in the loss of important historical data. With the optional CRON job for hands-free maintenance, adjustable settings for precision control, and insightful analytics, the Time-based Revision Cleanup plugin is an essential tool for maintaining a healthy, efficient WordPress site.\u003C\u002Fp>\n","Maximize WordPress efficiency with Time-based Revision Cleanup: manage post histories by age, not count, with optional auto-cleanups.",1908,"2026-02-15T22:51:00.000Z",[94,18,95,96,20],"cleanup","optimize","performance","https:\u002F\u002Fcompiledrogue.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftime-based-revisions.1.1.4.zip",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":107,"downloaded":108,"rating":107,"num_ratings":109,"last_updated":110,"tested_up_to":111,"requires_at_least":112,"requires_php":72,"tags":113,"homepage":116,"download_link":117,"security_score":56,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":118},"better-revisions","Better Revisions","0.5","slehner","https:\u002F\u002Fprofiles.wordpress.org\u002Fslehner\u002F","\u003Cp>Revisions are a main part of every content management system.\u003C\u002Fp>\n\u003Cp>Normal wordpress revisions only containing the title, content and excerpt. And WordPress by itself will only add a new revision, when one (or more) of these three fields were changed. This means, if someone only changes the permalink for example, then WordPress doesn’t add any revision. And if someone changes the content and maybe the author, then WordPress adds a revision, but only with the old content – the author change will be lost.\u003C\u002Fp>\n\u003Cp>For small blogs this will be ok, but what’s about multi-author websites or blogs?\u003C\u002Fp>\n\u003Cp>I wrote this small plugin for you – for a better revision management in multi-author blogs and sites, for better monitoring the changes of every site, post or custom-post-type and finally for better restoring older revisions.\u003C\u002Fp>\n\u003Cp>So, this plugin adds following fields to the revision system:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The Author\u003C\u002Fli>\n\u003Cli>Post Date\u003C\u002Fli>\n\u003Cli>Permalink\u003C\u002Fli>\n\u003Cli>Post Status\u003C\u002Fli>\n\u003Cli>Post Password\u003C\u002Fli>\n\u003Cli>Comment Status\u003C\u002Fli>\n\u003Cli>Ping Status\u003C\u002Fli>\n\u003Cli>Post\u002FPage Parent\u003C\u002Fli>\n\u003Cli>Menu Order\u003C\u002Fli>\n\u003Cli>more to come\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This Plugin also adds a new revision, if only one of the fields above were changed. And it works with automated post\u002Fpage saves (to the server) too. But I have disabled the client side autosave – becaus on multi-author blogs\u002Fsites these function makes no sense and confuses authors more than it helps. But the autosave to the server works perfectly well with all of the fields above added.\u003C\u002Fp>\n\u003Cp>If you want to restore a revision, the fields above will restored too. And in case of deleting a post\u002Fpage, than all revision with all fields above will be deleted too – for a smaller and cleaner database.\u003C\u002Fp>\n\u003Cp>No further configuration is needed, the plugin doesn’t add any database tables rather saves additional revision data to post-meta and works with custom-post-types too. It’s translation ready and allready translated into german.\u003C\u002Fp>\n\u003Ch4>Gutenberg support was added\u003C\u002Fh4>\n\u003Cp>Now it works with the new Block-Editoe (Gutenberg) and the old Classic-Editor (tinyMCE).\u003C\u002Fp>\n","Extend your Revisions: Add important fields like \"Permalink\" or \"Status\" to the revisions for a better Content Management.",90,8816,2,"2023-04-13T21:18:00.000Z","6.2.0","4.4",[18,114,115,53,20],"page-revision","post-revision","https:\u002F\u002Fwww.silvius.at\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbetter-revisions.0.5.zip","2026-04-06T09:54:40.288Z",{"slug":120,"name":121,"version":60,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":126,"downloaded":127,"rating":11,"num_ratings":11,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":72,"tags":131,"homepage":72,"download_link":136,"security_score":56,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"menus-history","Menus History","binarystash01","https:\u002F\u002Fprofiles.wordpress.org\u002Fbinarystash01\u002F","\u003Cp>The Menus History plugin provides history of changes to WordPress menus items. The history information may be useful in restoring deleted or misplaced menu items.\u003C\u002Fp>\n\u003Cp>To maximize the benefit of this plugin, install it on new WordPress set ups. The information it provides can be extremely useful particularly when database back-ups are not available. Once activated, it keeps track of the following.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Item arrangement\u003C\u002Fli>\n\u003Cli>Navigation labels\u003C\u002Fli>\n\u003Cli>Title attributes\u003C\u002Fli>\n\u003Cli>CSS classes\u003C\u002Fli>\n\u003Cli>Description\u003C\u002Fli>\n\u003Cli>URL\u003C\u002Fli>\n\u003Cli>Item targets\u003C\u002Fli>\n\u003Cli>Link relationships\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Please note the plugin’s limitations.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The plugin must be activated prior to making changes to your menus. Changes done before the plugin had been activated would not be shown. \u003C\u002Fli>\n\u003Cli>The plugin doesn’t provide the ability to restore menus; it only shows history information. You still need to manually restore your menus.\u003C\u002Fli>\n\u003Cli>Deleted menus are also removed from the plugin’s menu list.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Credits:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Hourglass icon made by \u003Ca href=\"http:\u002F\u002Fwww.freepik.com\" rel=\"nofollow ugc\">Freepik\u003C\u002Fa> from \u003Ca href=\"http:\u002F\u002Fwww.flaticon.com\" rel=\"nofollow ugc\">www.flaticon.com\u003C\u002Fa> is licensed under \u003Ca href=\"http:\u002F\u002Fcreativecommons.org\u002Flicenses\u002Fby\u002F3.0\u002F\" rel=\"nofollow ugc\">CC BY 3.0\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>List icon made by \u003Ca href=\"http:\u002F\u002Fwww.antonps.com\" rel=\"nofollow ugc\">Anton Saputro\u003C\u002Fa> from \u003Ca href=\"http:\u002F\u002Fwww.flaticon.com\" rel=\"nofollow ugc\">www.flaticon.com\u003C\u002Fa> is licensed under \u003Ca href=\"http:\u002F\u002Fcreativecommons.org\u002Flicenses\u002Fby\u002F3.0\u002F\" rel=\"nofollow ugc\">CC BY 3.0\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Provides history of changes to Wordpress menus",70,2837,"2015-05-24T07:23:00.000Z","4.2.39","3.5",[132,133,134,135,120],"menu-history","menu-revision","menu-revisions","menus","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmenus-history.1.0.2.zip",{"attackSurface":138,"codeSignals":159,"taintFlows":166,"riskAssessment":167,"analyzedAt":170},{"hooks":139,"ajaxHandlers":155,"restRoutes":156,"shortcodes":157,"cronEvents":158,"entryPointCount":11,"unprotectedCount":11},[140,146,152],{"type":141,"name":142,"callback":143,"file":144,"line":145},"action","gp_init","GlotCore\\HistoryLimiter\\gp_init","glotcore-history-limiter.php",45,{"type":141,"name":147,"callback":148,"priority":149,"file":150,"line":151},"gp_translation_saved","limit_waiting_translations",13,"src\u002Fclass-core.php",29,{"type":141,"name":147,"callback":153,"priority":29,"file":150,"line":154},"limit_old_translations",30,[],[],[],[],{"dangerousFunctions":160,"sqlUsage":161,"outputEscaping":163,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":11,"bundledLibraries":165},[],{"prepared":11,"raw":11,"locations":162},[],{"escaped":32,"rawEcho":11,"locations":164},[],[],[],{"summary":168,"deductions":169},"The 'glotcore-history-limiter' plugin version 1.0 exhibits an exceptionally strong security posture based on the provided static analysis. There are no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in a zero-attack surface. The code analysis further reveals a complete absence of dangerous functions, file operations, external HTTP requests, and crucially, it utilizes prepared statements for all SQL queries and properly escapes all outputs. This indicates a robust development process that prioritizes secure coding practices. The plugin also has no known vulnerabilities in its history, further reinforcing its secure standing.  While the lack of capability checks and nonce checks is a technical absence, given the complete lack of entry points and known vulnerabilities, this does not immediately present a risk in the current version. The plugin is currently well-secured.",[],"2026-04-16T13:43:45.863Z",{"wat":172,"direct":181},{"assetPaths":173,"generatorPatterns":176,"scriptPaths":177,"versionParams":178},[174,175],"\u002Fwp-content\u002Fplugins\u002Fglotcore-history-limiter\u002Fassets\u002Fcss\u002Fstyle.css","\u002Fwp-content\u002Fplugins\u002Fglotcore-history-limiter\u002Fassets\u002Fjs\u002Fscript.js",[],[175],[179,180],"glotcore-history-limiter\u002Fassets\u002Fcss\u002Fstyle.css?ver=","glotcore-history-limiter\u002Fassets\u002Fjs\u002Fscript.js?ver=",{"cssClasses":182,"htmlComments":183,"htmlAttributes":184,"restEndpoints":185,"jsGlobals":186,"shortcodeOutput":187},[],[],[],[],[],[],{"error":189,"url":190,"statusCode":191,"statusMessage":192,"message":192},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fglotcore-history-limiter\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":32,"versions":194},[195],{"version":6,"download_url":22,"svn_tag_url":196,"released_at":24,"has_diff":197,"diff_files_changed":198,"diff_lines":24,"trac_diff_url":24,"vulnerabilities":199,"is_current":189},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fglotcore-history-limiter\u002Ftags\u002F1.0\u002F",false,[],[]]