[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fTD8bYXux6NdPfkWouW5TdLDxsHEhJZHDYCFQCoGAQ1Y":3,"$fpspIiFv80zYoFGaxyK-6meucAhzM2s8Q758RO0BJ8fY":405,"$fj1PwQBpxvCujoBzpYTDsk3_6hF8vKibdD7jxeWUGo2o":410},{"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":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":37,"analysis":133,"fingerprints":350},"lh-tools","LH Tools","0.15","shawfactor","https:\u002F\u002Fprofiles.wordpress.org\u002Fshawfactor\u002F","\u003Cp>LH Tools is a wordpress plugin that enables a sparql endpoint for for WordPress sites. This will enable sematic querying of WordPress data either from the site itself or from external providers of RDF triples.\u003C\u002Fp>\n","LH Tools is a wordpress plugin that enables a sparql endpoint for for WordPress sites. This will enable semantic querying of WordPress data.",10,2417,0,"2015-04-24T09:01:00.000Z","4.2.39","3.0","",[19,20,21,22,23],"json","localhero","rdf","skos","sparql","http:\u002F\u002Flhero.org\u002Fplugins\u002Flh-tools\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flh-tools.zip",85,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":26,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},89,14520,7,90,"2026-05-19T19:14:33.475Z",[38,54,66,86,109],{"slug":39,"name":40,"version":41,"author":7,"author_profile":8,"description":42,"short_description":43,"active_installs":11,"downloaded":44,"rating":35,"num_ratings":45,"last_updated":46,"tested_up_to":47,"requires_at_least":16,"requires_php":17,"tags":48,"homepage":52,"download_link":53,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"lh-rdf","LH RDF","1.21","\u003Cp>It has been developed for use in \u003Ca href=\"http:\u002F\u002Flocalhero.biz\u002F\" rel=\"nofollow ugc\">LocalHero\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Once activated the plugin adds a new type of feed that can be subscribed to. E.G. http:\u002F\u002Flocalhero.biz\u002F?feed=lhrdf or http:\u002F\u002Flocalhero.biz\u002Ffeed\u002Flhrdf\u002F containing semantic content.\u003C\u002Fp>\n\u003Cp>To output the feed in other triple formats just add the get variable format= to the query string E.G. http:\u002F\u002Flocalhero.biz\u002F?feed=lhrdf&format=json.\u003C\u002Fp>\n\u003Cp>Ontologies exposed in the RDF output include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>RDF: Resource Description Framework Ontology;\u003C\u002Fli>\n\u003Cli>SIOC: Semantically-Interlinked Online Communities Ontology;\u003C\u002Fli>\n\u003Cli>OAI-ORE Vocabulary for Resource Aggregation;\u003C\u002Fli>\n\u003Cli>DCTerms: Dublin Core Metadata Ontology;\u003C\u002Fli>\n\u003Cli>FOAF: Friend of a Friend Ontology;\u003C\u002Fli>\n\u003Cli>SKOS: Simple Knowledge Organization System Ontology;\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin also allows you to map user and post meta as rdf properties. It will also allow connect created via the plugin Posts 2 Posts to rdf properties via configurable settings.\u003C\u002Fp>\n","This plugin publishes your weblog as RDF in multiple formats (xml, turtle, json etc). Mapping WordPress objects to the major ontologies.",3790,2,"2015-08-21T17:17:00.000Z","4.3.34",[49,50,20,21,51],"feed","feeds","sioc","http:\u002F\u002Flhero.org\u002Fplugins\u002Flh-rdf\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flh-rdf.zip",{"slug":55,"name":56,"version":57,"author":7,"author_profile":8,"description":58,"short_description":59,"active_installs":11,"downloaded":60,"rating":13,"num_ratings":13,"last_updated":61,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":62,"homepage":63,"download_link":64,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":65},"lh-relationships","LH Relationships","0.21","\u003Cp>Once activated the plugin allow semantic relationships to be created between any post type. It has been developed for use in \u003Ca href=\"http:\u002F\u002Flocalhero.biz\u002F\" rel=\"nofollow ugc\">LocalHero\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>For detailed information on the plugin, what it does, and what it can be used to build visit the \u003Ca href=\"http:\u002F\u002Flocalhero.biz\u002Fplugins\u002Flh-relationships\u002F\" rel=\"nofollow ugc\">lh-relationships\u003C\u002Fa> info page.\u003C\u002Fp>\n","This plugin allows allows the creation and publishing of triple relationships in RDF format.",2013,"2015-04-24T08:59:00.000Z",[49,50,20,21,51],"http:\u002F\u002Flocalhero.biz\u002Fplugins\u002Flh-relationships\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flh-relationships.zip","2026-03-15T15:16:48.613Z",{"slug":67,"name":68,"version":69,"author":70,"author_profile":71,"description":72,"short_description":73,"active_installs":11,"downloaded":74,"rating":75,"num_ratings":76,"last_updated":77,"tested_up_to":78,"requires_at_least":79,"requires_php":17,"tags":80,"homepage":84,"download_link":85,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"poolparty-thesaurus","PoolParty Thesaurus","2.8","kurt-moser","https:\u002F\u002Fprofiles.wordpress.org\u002Fkurt-moser\u002F","\u003Cp>PoolParty thesaurus plugin helps to make WordPress blogs and websites more understandable. The website will be improved by linking posts with key terms and key terms with other key terms. The plugin imports a controlled vocabulary (SKOS thesaurus) or retrieves a thesaurus from a (public) SPARQL endpoint via web. Based on the thesaurus, terms in articles are high-lighted automatically, definitions are provided “inline” (as mouse-over effect) and links to the thesaurus terms are generated on-the-fly. The thesaurus is available as an extra resource on the blog and can be navigated to learn more about the knowledge domain instantly. The plugin also works with multilingual blogs. Dbpedia (Linked data) is used to retrieve definitions automatically whenever the imported thesaurus lacks of definitions.\u003C\u002Fp>\n\u003Cp>With this plugin any SKOS\u002FRDF thesaurus can be imported or retrieved from a SPARQL endpoint and used within your WordPress blog to underpin articles with key terms.\u003C\u002Fp>\n\u003Cp>On two extra pages (which are generated automatically) the thesaurus can be displayed and used as a browsable glossary on your blog. The main page of the glossary displays all concepts with their preferred labels and their alternative labels (synonyms). The list of concepts is displayed in an alphabetical order and can be filtered by their first letters. The second page represents the detail view of each concept. All kinds of labels and relations (prefLabel, altLabel, hiddenLabel, definition, scopNote, broader, narrower und related) of a given term (concept) can be loaded and displayed.\u003C\u002Fp>\n\u003Cp>Each post is analysed automatically to find words and phrases matching labels of a concept (prefLabel, altLabel or hiddenLabel) in the thesaurus. The first hit will be highlighted automatically. A mousover tooltip shows the short description of the term\u002Fphrase and the link points to the more detailed description on the glossary page.\u003C\u002Fp>\n\u003Ch4>Shortcodes\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[ppt-abcindex]: displays an abc filter for filtering the concepts alphabetically.\u003C\u002Fli>\n\u003Cli>[ppt-itemlist]: displays a list of concepts (filterd by its first letter).\u003C\u002Fli>\n\u003Cli>[ppt-itemdetails]: displays the detail page of a selected concept.\u003C\u002Fli>\n\u003Cli>[ppt-noparse] … [\u002Fppt-noparse]: the content between of the shortcode is excluded from autmatic linking.\u003C\u002Fli>\n\u003Cli>[ppt-searchform title=”…” width=”…[ px | % ]”]: displays a search form with a autocomplete field to find a concept.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What’s new?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>The Plugin works now with the user-friendly multilingual dynamic content management \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fqtranslate-x\u002F\" rel=\"ugc\">qTranslate X\u003C\u002Fa> for a multilingual WordPress\u003C\u002Fli>\n\u003Cli>The URL to the detail page of a concept is now SEO optimized \u003C\u002Fli>\n\u003Cli>The search algorithm behind the search link on top of the concept detail page is extended (searches now for prefered and alternative labels)\u003C\u002Fli>\n\u003Cli>Implemented new shortcode with which you can add a simple glossary search form between content. The shortcode is called [ppt-searchform] and has two optional parameters: title (The title over the textfield. Leave blank if you don’t want a title) and width (The width of the textfield). An example: [ppt-searchform title=”Glossary search” width=”50%”]\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Thanks to Benjamin Nowack: The thesaurus is imported into the system and is queried via ARC2 (https:\u002F\u002Fgithub.com\u002Fsemsol\u002Farc2).\u003Cbr \u002F>\nThanks to rduffy (https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fprofile\u002Frduffy). His ‘Glossary’ Plugin (https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fautomatic-glossary) inspired me, and I was able to develop this plugin on top of his ideas.\u003C\u002Fp>\n\u003Cp>Works with PHP 5, MySQL 5 und ARC2\u003C\u002Fp>\n","PoolParty plugin makes websites more understandable. Blogs benefit from linking posts with key terms automatically. The plugin uses SKOS vocabularies",4743,54,3,"2019-03-18T14:25:00.000Z","5.1.22","3.1",[81,82,21,22,83],"glossary","poolparty","thesaurus","https:\u002F\u002Fwww.poolparty.biz","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpoolparty-thesaurus.2.8.zip",{"slug":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":94,"downloaded":95,"rating":96,"num_ratings":97,"last_updated":98,"tested_up_to":99,"requires_at_least":100,"requires_php":101,"tags":102,"homepage":107,"download_link":108,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"disable-json-api","Disable REST API","1.8","Dave McHale","https:\u002F\u002Fprofiles.wordpress.org\u002Fdmchale\u002F","\u003Cp>The most comprehensive plugin for controlling access to the WordPress REST API!\u003C\u002Fp>\n\u003Cp>Works as a “set it and forget it” install. Just upload and activate, and the entire REST API will be inaccessible to your general site visitors.\u003C\u002Fp>\n\u003Cp>But if you do need to grant access to some endpoints, you can do that too. Go to the Settings page and you can quickly whitelist individual endpoints (or entire branches of endpoints) in the REST API.\u003C\u002Fp>\n\u003Cp>You can even do this on a per-user-role basis, so your unauthenticated users have one set of rules while WooCommerce customers have another while Subscribers and Editors and Admins all have their own. NOTE: Out of the box, all defined user roles will still be granted full access to the REST API until you choose to manage those settings.\u003C\u002Fp>\n\u003Cp>For most versions of WordPress, this plugin will return an authentication error if a user is not allowed to access an endpoint. For legacy support, WordPress 4.4, 4.5, and 4.6 use the provided \u003Ccode>rest_enabled\u003C\u002Fcode> filter to disable the entire REST API.\u003C\u002Fp>\n","Disable the use of the REST API on your website to site users. Now with User Role support!",90000,758515,96,38,"2023-09-14T00:26:00.000Z","6.3.8","4.9","5.6",[103,104,19,105,106],"admin","api","rest","rest-api","http:\u002F\u002Fwww.binarytemplar.com\u002Fdisable-json-api","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-json-api.zip",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":117,"downloaded":118,"rating":119,"num_ratings":120,"last_updated":121,"tested_up_to":122,"requires_at_least":123,"requires_php":124,"tags":125,"homepage":130,"download_link":131,"security_score":132,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"jwt-authentication-for-wp-rest-api","JWT Authentication for WP REST API","1.5.0","tmeister","https:\u002F\u002Fprofiles.wordpress.org\u002Ftmeister\u002F","\u003Cp>This plugin seamlessly extends the WP REST API, enabling robust and secure authentication using JSON Web Tokens (JWT). It provides a straightforward way to authenticate users via the REST API, returning a standard JWT upon successful login.\u003C\u002Fp>\n\u003Ch3>Key features of this free version include:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Standard JWT Authentication:\u003C\u002Fstrong> Implements the industry-standard \u003Ca href=\"https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7519\" rel=\"nofollow ugc\">RFC 7519\u003C\u002Fa> for secure claims representation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Simple Endpoints:\u003C\u002Fstrong> Offers clear \u003Ccode>\u002Ftoken\u003C\u002Fcode> and \u003Ccode>\u002Ftoken\u002Fvalidate\u003C\u002Fcode> endpoints for generating and validating tokens.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Configurable Secret Key:\u003C\u002Fstrong> Define your unique secret key via \u003Ccode>wp-config.php\u003C\u002Fcode> for secure token signing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Optional CORS Support:\u003C\u002Fstrong> Easily enable Cross-Origin Resource Sharing support via a \u003Ccode>wp-config.php\u003C\u002Fcode> constant.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Developer Hooks:\u003C\u002Fstrong> Provides filters (\u003Ccode>jwt_auth_expire\u003C\u002Fcode>, \u003Ccode>jwt_auth_token_before_sign\u003C\u002Fcode>, etc.) for customizing token behavior.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>JSON Web Tokens are an open, industry standard method for representing claims securely between two parties.\u003C\u002Fp>\n\u003Cp>For users requiring more advanced capabilities such as multiple signing algorithms (RS256, ES256), token refresh\u002Frevocation, UI-based configuration, or priority support, consider checking out \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_link_soft\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Support and Requests:\u003C\u002Fstrong> Please use \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FTmeister\u002Fwp-api-jwt-auth\u002Fissues\" rel=\"nofollow ugc\">GitHub Issues\u003C\u002Fa>. For priority support, consider upgrading to \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_support_link\" rel=\"nofollow ugc\">PRO\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>REQUIREMENTS\u003C\u002Fh3>\n\u003Ch4>WP REST API V2\u003C\u002Fh4>\n\u003Cp>This plugin was conceived to extend the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWP-API\u002FWP-API\" rel=\"nofollow ugc\">WP REST API V2\u003C\u002Fa> plugin features and, of course, was built on top of it.\u003C\u002Fp>\n\u003Cp>So, to use the \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> you need to install and activate \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWP-API\u002FWP-API\" rel=\"nofollow ugc\">WP REST API\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>PHP\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Minimum PHP version: 7.4.0\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>PHP HTTP Authorization Header Enable\u003C\u002Fh3>\n\u003Cp>Most shared hosting providers have disabled the \u003Cstrong>HTTP Authorization Header\u003C\u002Fstrong> by default.\u003C\u002Fp>\n\u003Cp>To enable this option you’ll need to edit your \u003Cstrong>.htaccess\u003C\u002Fstrong> file by adding the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>RewriteEngine on\nRewriteCond %{HTTP:Authorization} ^(.*)\nRewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>WPENGINE\u003C\u002Fh4>\n\u003Cp>For WPEngine hosting, you’ll need to edit your \u003Cstrong>.htaccess\u003C\u002Fstrong> file by adding the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>SetEnvIf Authorization \"(.*)\" HTTP_AUTHORIZATION=$1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>See https:\u002F\u002Fgithub.com\u002FTmeister\u002Fwp-api-jwt-auth\u002Fissues\u002F1 for more details.\u003C\u002Fp>\n\u003Ch3>CONFIGURATION\u003C\u002Fh3>\n\u003Ch3>Configure the Secret Key\u003C\u002Fh3>\n\u003Cp>The JWT needs a \u003Cstrong>secret key\u003C\u002Fstrong> to sign the token. This \u003Cstrong>secret key\u003C\u002Fstrong> must be unique and never revealed.\u003C\u002Fp>\n\u003Cp>To add the \u003Cstrong>secret key\u003C\u002Fstrong>, edit your wp-config.php file and add a new constant called \u003Cstrong>JWT_AUTH_SECRET_KEY\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('JWT_AUTH_SECRET_KEY', 'your-top-secret-key');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can generate a secure key from: https:\u002F\u002Fapi.wordpress.org\u002Fsecret-key\u002F1.1\u002Fsalt\u002F\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Looking for easier configuration?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=config_secret_key_link\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> allows you to manage all settings through a simple admin UI.\u003C\u002Fp>\n\u003Ch3>Configure CORS Support\u003C\u002Fh3>\n\u003Cp>The \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> plugin has the option to activate \u003Ca href=\"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCross-origin_resource_sharing\" rel=\"nofollow ugc\">CORS\u003C\u002Fa> support.\u003C\u002Fp>\n\u003Cp>To enable CORS Support, edit your wp-config.php file and add a new constant called \u003Cstrong>JWT_AUTH_CORS_ENABLE\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('JWT_AUTH_CORS_ENABLE', true);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Finally, activate the plugin within your wp-admin.\u003C\u002Fp>\n\u003Ch3>Namespace and Endpoints\u003C\u002Fh3>\n\u003Cp>When the plugin is activated, a new namespace is added:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002Fjwt-auth\u002Fv1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Also, two new endpoints are added to this namespace:\u003C\u002Fp>\n\u003Cp>Endpoint | HTTP Verb\u003Cbr \u002F>\n\u003Cem>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u003C\u002Fem> | POST\u003Cbr \u002F>\n\u003Cem>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u002Fvalidate\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Need more functionality?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=endpoints_pro_note\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> includes additional endpoints for token refresh and revocation.\u003C\u002Fp>\n\u003Ch3>USAGE\u003C\u002Fh3>\n\u003Ch4>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u003C\u002Fh4>\n\u003Cp>This is the entry point for JWT Authentication.\u003C\u002Fp>\n\u003Cp>It validates the user credentials, \u003Cem>username\u003C\u002Fem> and \u003Cem>password\u003C\u002Fem>, and returns a token to use in future requests to the API if the authentication is correct, or an error if authentication fails.\u003C\u002Fp>\n\u003Cp>Sample Request Using AngularJS\u003C\u002Fp>\n\u003Cpre>\u003Ccode>(function() {\n  var app = angular.module('jwtAuth', []);\n\n  app.controller('MainController', function($scope, $http) {\n    var apiHost = 'http:\u002F\u002Fyourdomain.com\u002Fwp-json';\n\n    $http.post(apiHost + '\u002Fjwt-auth\u002Fv1\u002Ftoken', {\n      username: 'admin',\n      password: 'password'\n    })\n    .then(function(response) {\n      console.log(response.data)\n    })\n    .catch(function(error) {\n      console.error('Error', error.data[0]);\n    });\n  });\n})();\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Success Response From The Server\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"token\": \"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC9qd3QuZGV2IiwiaWF0IjoxNDM4NTcxMDUwLCJuYmYiOjE0Mzg1NzEwNTAsImV4cCI6MTQzOTE3NTg1MCwiZGF0YSI6eyJ1c2VyIjp7ImlkIjoiMSJ9fX0.YNe6AyWW4B7ZwfFE5wJ0O6qQ8QFcYizimDmBy6hCH_8\",\n  \"user_display_name\": \"admin\",\n  \"user_email\": \"admin@localhost.dev\",\n  \"user_nicename\": \"admin\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Error Response From The Server\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"code\": \"jwt_auth_failed\",\n  \"data\": {\n    \"status\": 403\n  },\n  \"message\": \"Invalid Credentials.\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Once you get the token, you must store it somewhere in your application, e.g., in a \u003Cstrong>cookie\u003C\u002Fstrong> or using \u003Cstrong>localStorage\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>From this point, you should pass this token with every API call.\u003C\u002Fp>\n\u003Cp>Sample Call Using The Authorization Header With AngularJS\u003C\u002Fp>\n\u003Cpre>\u003Ccode>app.config(function($httpProvider) {\n  $httpProvider.interceptors.push(['$q', '$location', '$cookies', function($q, $location, $cookies) {\n    return {\n      'request': function(config) {\n        config.headers = config.headers || {};\n        \u002F\u002F Assume that you store the token in a cookie\n        var globals = $cookies.getObject('globals') || {};\n        \u002F\u002F If the cookie has the CurrentUser and the token\n        \u002F\u002F add the Authorization header in each request\n        if (globals.currentUser && globals.currentUser.token) {\n          config.headers.Authorization = 'Bearer ' + globals.currentUser.token;\n        }\n        return config;\n      }\n    };\n  }]);\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> plugin will intercept every call to the server and will look for the Authorization Header. If the Authorization header is present, it will try to decode the token and will set the user according to the data stored in it.\u003C\u002Fp>\n\u003Cp>If the token is valid, the API call flow will continue as normal.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Sample Headers\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>POST \u002Fresource HTTP\u002F1.1\nHost: server.example.com\nAuthorization: Bearer mF_s9.B5f-4.1JqM\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>ERRORS\u003C\u002Fh3>\n\u003Cp>If the token is invalid, an error will be returned. Here are some sample errors:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Invalid Credentials\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[\n  {\n    \"code\": \"jwt_auth_failed\",\n    \"message\": \"Invalid Credentials.\",\n    \"data\": {\n      \"status\": 403\n    }\n  }\n]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Invalid Signature\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[\n  {\n    \"code\": \"jwt_auth_invalid_token\",\n    \"message\": \"Signature verification failed\",\n    \"data\": {\n      \"status\": 403\n    }\n  }\n]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Expired Token\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[\n  {\n    \"code\": \"jwt_auth_invalid_token\",\n    \"message\": \"Expired token\",\n    \"data\": {\n      \"status\": 403\n    }\n  }\n]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Need advanced error tracking?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=errors_pro_note\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> offers enhanced error tracking and monitoring capabilities.\u003C\u002Fp>\n\u003Ch4>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u002Fvalidate\u003C\u002Fh4>\n\u003Cp>This is a simple helper endpoint to validate a token. You only need to make a POST request with the Authorization header.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Valid Token Response\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"code\": \"jwt_auth_valid_token\",\n  \"data\": {\n    \"status\": 200\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>AVAILABLE HOOKS\u003C\u002Fh3>\n\u003Cp>The \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> plugin is developer-friendly and provides five filters to override the default settings.\u003C\u002Fp>\n\u003Ch4>jwt_auth_cors_allow_headers\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_cors_allow_headers\u003C\u002Fstrong> filter allows you to modify the available headers when CORS support is enabled.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'Access-Control-Allow-Headers, Content-Type, Authorization'\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_not_before\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_not_before\u003C\u002Fstrong> filter allows you to change the \u003Ca href=\"https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7519#section-4.1.5\" rel=\"nofollow ugc\">\u003Cstrong>nbf\u003C\u002Fstrong>\u003C\u002Fa> value before the token is created.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Creation time - time()\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_expire\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_expire\u003C\u002Fstrong> filter allows you to change the \u003Ca href=\"https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7519#section-4.1.4\" rel=\"nofollow ugc\">\u003Cstrong>exp\u003C\u002Fstrong>\u003C\u002Fa> value before the token is created.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>time() + (DAY_IN_SECONDS * 7)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_token_before_sign\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_token_before_sign\u003C\u002Fstrong> filter allows you to modify all token data before it is encoded and signed.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$token = array(\n    'iss' => get_bloginfo('url'),\n    'iat' => $issuedAt,\n    'nbf' => $notBefore,\n    'exp' => $expire,\n    'data' => array(\n        'user' => array(\n            'id' => $user->data->ID,\n        )\n    )\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Want easier customization?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=hook_payload_pro_note\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> allows you to add custom claims directly through the admin UI.\u003C\u002Fp>\n\u003Ch4>jwt_auth_token_before_dispatch\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_token_before_dispatch\u003C\u002Fstrong> filter allows you to modify the response array before it is sent to the client.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$data = array(\n    'token' => $token,\n    'user_email' => $user->data->user_email,\n    'user_nicename' => $user->data->user_nicename,\n    'user_display_name' => $user->data->display_name,\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_algorithm\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_algorithm\u003C\u002Fstrong> filter allows you to modify the signing algorithm.\u003C\u002Fp>\n\u003Cp>Default value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$token = JWT::encode(\n    apply_filters('jwt_auth_token_before_sign', $token, $user),\n    $secret_key,\n    apply_filters('jwt_auth_algorithm', 'HS256')\n);\n\n\u002F\u002F ...\n\n$token = JWT::decode(\n    $token,\n    new Key($secret_key, apply_filters('jwt_auth_algorithm', 'HS256'))\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>JWT Authentication PRO\u003C\u002Fh3>\n\u003Cp>Elevate your WordPress security and integration capabilities with \u003Cstrong>JWT Authentication PRO\u003C\u002Fstrong>. Building upon the solid foundation of the free version, the PRO version offers advanced features, enhanced security options, and a streamlined user experience:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Easy Configuration UI:\u003C\u002Fstrong> Manage all settings directly from the WordPress admin area.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Refresh Endpoint:\u003C\u002Fstrong> Allow users to refresh expired tokens seamlessly without requiring re-login.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Revocation Endpoint:\u003C\u002Fstrong> Immediately invalidate specific tokens for enhanced security control.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Customizable Token Payload:\u003C\u002Fstrong> Add custom claims to your JWT payload to suit your specific application needs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Granular CORS Control:\u003C\u002Fstrong> Define allowed origins and headers with more precision directly in the settings.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rate Limiting:\u003C\u002Fstrong> Protect your endpoints from abuse with configurable rate limits.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit Logs:\u003C\u002Fstrong> Keep track of token generation, validation, and errors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Priority Support:\u003C\u002Fstrong> Get faster, dedicated support directly from the developer.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=pro_section_cta\" rel=\"nofollow ugc\">Upgrade to JWT Authentication PRO Today!\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Free vs. PRO Comparison\u003C\u002Fh3>\n\u003Cp>Here’s a quick look at the key differences:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Basic JWT Authentication:\u003C\u002Fstrong> Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Generation:\u003C\u002Fstrong> Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Validation:\u003C\u002Fstrong> Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Refresh Mechanism:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Revocation:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Management Dashboard:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Analytics & Monitoring:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Geo-IP Identification:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rate Limiting:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detailed Documentation:\u003C\u002Fstrong> Basic (Free), Comprehensive (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Developer Tools:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Premium Support:\u003C\u002Fstrong> Community via GitHub (Free), Priority Direct Support (PRO)\u003C\u002Fli>\n\u003C\u002Ful>\n","Extends the WP REST API using JSON Web Tokens Authentication as an authentication method.",60000,906385,88,53,"2026-02-18T00:58:00.000Z","6.9.4","4.2","7.4.0",[126,127,128,106,129],"json-web-authentication","jwt","oauth","wp-api","https:\u002F\u002Fenriquechavez.co","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjwt-authentication-for-wp-rest-api.1.5.0.zip",100,{"attackSurface":134,"codeSignals":184,"taintFlows":255,"riskAssessment":331,"analyzedAt":349},{"hooks":135,"ajaxHandlers":170,"restRoutes":171,"shortcodes":172,"cronEvents":181,"entryPointCount":45,"unprotectedCount":13},[136,142,146,150,155,159,162,167],{"type":137,"name":138,"callback":139,"file":140,"line":141},"action","admin_menu","lh_tools_handle_admin_request","lh-tools.php",77,{"type":137,"name":143,"callback":144,"file":140,"line":145},"lh_tools_load_endpoint_hourly","lh_tools_load_endpoint",596,{"type":137,"name":147,"callback":148,"file":140,"line":149},"wp","lh_tools_endpoint_activation",606,{"type":151,"name":152,"callback":153,"file":140,"line":154},"filter","xmlrpc_methods","lh_tools_new_xmlrpc_methods",663,{"type":137,"name":156,"callback":157,"file":140,"line":158},"init","lh_tools_init_external_form_handler",675,{"type":137,"name":156,"callback":160,"file":140,"line":161},"lh_tools_init_external_api_handler",687,{"type":137,"name":163,"callback":164,"file":165,"line":166},"plugins_loaded","lh_tools_article_map_widget_init","library\u002Fthe_widgets.php",43,{"type":137,"name":163,"callback":168,"file":165,"line":169},"lh_tools_related_articles_widget_init",83,[],[],[173,177],{"tag":174,"callback":175,"file":165,"line":176},"lh_tools_article_map_shortcode","lh_tools_article_map_short_func",26,{"tag":178,"callback":179,"file":165,"line":180},"lh_tools_related_articles_shortcode","lh_tools_related_articles_short_func",67,[182],{"hook":143,"callback":143,"file":140,"line":183},601,{"dangerousFunctions":185,"sqlUsage":194,"outputEscaping":197,"fileOperations":45,"externalRequests":45,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":254},[186,190,192],{"fn":187,"file":140,"line":188,"context":189},"exec",378,"exec($sCmd, $aOutput, $iResult);",{"fn":187,"file":140,"line":191,"context":189},387,{"fn":187,"file":140,"line":193,"context":189},400,{"prepared":195,"raw":13,"locations":196},18,[],{"escaped":13,"rawEcho":198,"locations":199},27,[200,203,205,207,209,211,213,215,218,220,222,224,226,228,230,232,235,236,238,240,242,244,246,248,249,250,252],{"file":140,"line":201,"context":202},119,"raw output",{"file":140,"line":204,"context":202},461,{"file":140,"line":206,"context":202},465,{"file":140,"line":208,"context":202},469,{"file":140,"line":210,"context":202},494,{"file":140,"line":212,"context":202},498,{"file":140,"line":214,"context":202},556,{"file":216,"line":217,"context":202},"library\u002Ffunctions.php",5,{"file":216,"line":219,"context":202},41,{"file":216,"line":221,"context":202},47,{"file":216,"line":223,"context":202},51,{"file":216,"line":225,"context":202},62,{"file":216,"line":227,"context":202},98,{"file":165,"line":229,"context":202},32,{"file":165,"line":231,"context":202},72,{"file":233,"line":234,"context":202},"php.php",46,{"file":233,"line":221,"context":202},{"file":233,"line":237,"context":202},157,{"file":239,"line":234,"context":202},"ping.php",{"file":239,"line":241,"context":202},56,{"file":239,"line":243,"context":202},60,{"file":239,"line":245,"context":202},68,{"file":239,"line":247,"context":202},80,{"file":239,"line":119,"context":202},{"file":239,"line":96,"context":202},{"file":239,"line":251,"context":202},110,{"file":239,"line":253,"context":202},116,[],[256,275,283,304],{"entryPoint":257,"graph":258,"unsanitizedCount":273,"severity":274},"rdf_tools_handle_options_submit (lh-tools.php:280)",{"nodes":259,"edges":270},[260,265],{"id":261,"type":262,"label":263,"file":140,"line":264},"n0","source","$_POST[$k]",297,{"id":266,"type":267,"label":268,"file":140,"line":264,"wp_function":269},"n1","sink","update_option() [Settings Manipulation]","update_option",[271],{"from":261,"to":266,"sanitized":272},false,1,"low",{"entryPoint":276,"graph":277,"unsanitizedCount":273,"severity":274},"\u003Clh-tools> (lh-tools.php:0)",{"nodes":278,"edges":281},[279,280],{"id":261,"type":262,"label":263,"file":140,"line":264},{"id":266,"type":267,"label":268,"file":140,"line":264,"wp_function":269},[282],{"from":261,"to":266,"sanitized":272},{"entryPoint":284,"graph":285,"unsanitizedCount":45,"severity":303},"\u003Cphp> (php.php:0)",{"nodes":286,"edges":300},[287,290,294,296],{"id":261,"type":262,"label":288,"file":233,"line":289},"$_GET",149,{"id":266,"type":267,"label":291,"file":233,"line":292,"wp_function":293},"query() [SQLi]",153,"query",{"id":295,"type":262,"label":288,"file":233,"line":289},"n2",{"id":297,"type":267,"label":298,"file":233,"line":237,"wp_function":299},"n3","echo() [XSS]","echo",[301,302],{"from":261,"to":266,"sanitized":272},{"from":295,"to":297,"sanitized":272},"high",{"entryPoint":305,"graph":306,"unsanitizedCount":330,"severity":303},"\u003Cping> (ping.php:0)",{"nodes":307,"edges":325},[308,311,312,314,315,319,323],{"id":261,"type":262,"label":309,"file":239,"line":310},"$_POST (x7)",44,{"id":266,"type":267,"label":298,"file":239,"line":234,"wp_function":299},{"id":295,"type":262,"label":313,"file":239,"line":310},"$_POST (x5)",{"id":297,"type":267,"label":291,"file":239,"line":225,"wp_function":293},{"id":316,"type":262,"label":317,"file":239,"line":318},"n4","$_POST",74,{"id":320,"type":321,"label":322,"file":239,"line":318},"n5","transform","→ lh_tools_taxmapper_client()",{"id":324,"type":267,"label":298,"file":216,"line":217,"wp_function":299},"n6",[326,327,328,329],{"from":261,"to":266,"sanitized":272},{"from":295,"to":297,"sanitized":272},{"from":316,"to":320,"sanitized":272},{"from":320,"to":324,"sanitized":272},13,{"summary":332,"deductions":333},"The \"lh-tools\" plugin v0.15 presents a mixed security posture. While it demonstrates good practices like using prepared statements for all SQL queries and having no known CVEs, significant concerns arise from its static analysis. The complete absence of nonce checks and capability checks, coupled with the presence of the `exec` dangerous function and unsanitized path taint flows, creates potential avenues for malicious exploitation. The fact that 100% of its outputs are not properly escaped is also a serious weakness, potentially leading to Cross-Site Scripting (XSS) vulnerabilities.  The plugin has no recorded vulnerability history, which is a positive sign, but this cannot fully mitigate the risks identified in the current code. The limited attack surface and zero unprotected entry points are commendable, but the identified code signals and taint analysis suggest that if an attacker could find a way to trigger these flaws, the impact could be severe.",[334,337,339,341,343,345,347],{"reason":335,"points":336},"Dangerous function `exec` found",15,{"reason":338,"points":336},"Unsanitized path taint flows found (2 high severity)",{"reason":340,"points":11},"No nonce checks present",{"reason":342,"points":11},"No capability checks present",{"reason":344,"points":336},"0% output properly escaped",{"reason":346,"points":217},"2 file operations found",{"reason":348,"points":217},"2 external HTTP requests found","2026-04-16T12:46:27.534Z",{"wat":351,"direct":360},{"assetPaths":352,"generatorPatterns":357,"scriptPaths":358,"versionParams":359},[353,354,355,356],"\u002Fwp-content\u002Fplugins\u002Flh-tools\u002Farc\u002Fjs\u002Farc.js","\u002Fwp-content\u002Fplugins\u002Flh-tools\u002Farc\u002Fjs\u002Farc.min.js","\u002Fwp-content\u002Fplugins\u002Flh-tools\u002Fcss\u002Flh-tools.css","\u002Fwp-content\u002Fplugins\u002Flh-tools\u002Fjs\u002Flh-tools.js",[],[353,354,356],[],{"cssClasses":361,"htmlComments":364,"htmlAttributes":376,"restEndpoints":393,"jsGlobals":395,"shortcodeOutput":404},[362,363],"rdf-tools","form-item",[365,366,367,368,369,370,371,372,373,374,375],"== Changelog ==","License:","Copyright 2011  Peter Shaw  (email : pete@localhero.biz)","This program is free software; you can redistribute it and\u002For modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.","This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.","You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA","\u002F* hooks *\u002F","\u002F* defines *\u002F","\u002F* includes *\u002F","\u002F* init *\u002F","\u002F* admin *\u002F",[377,378,379,380,381,382,383,384,385,386,387,388,389,390,391,392],"name=\"store_setup\"","id=\"store_setup\"","name=\"store_reset\"","id=\"store_reset\"","name=\"store_drop\"","id=\"store_drop\"","name=\"endpoint_active\"","id=\"endpoint_active\"","name=\"endpoint_max_limit\"","id=\"endpoint_max_limit\"","id=\"endpoint_read_key\"","name=\"endpoint_read_key\"","id=\"endpoint_write_key\"","name=\"endpoint_write_key\"","id=\"endpoint_src_file\"","name=\"endpoint_src_file\"",[394],"\u002Fwp-json\u002Flh-tools\u002F",[396,397,398,399,400,401,402,403],"rdf_tools_get_token","rdf_tools_handle_options_submit","rdf_tools_get_store_options_fields","lh_tools_get_lh_rdf_get_link","lh_rdf_get_link","rdf_tools_get_endpoint_options_fields","rdf_tools_get_setting","rdf_tools_get_endpoint_features_fields",[],{"error":406,"url":407,"statusCode":408,"statusMessage":409,"message":409},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Flh-tools\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":13,"versions":411},[]]