[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fmadS0pQICPbTC9hcIq8W9Jt59NFTJBUj747hCQZ_X7s":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"rioriost","https:\u002F\u002Fprofiles.wordpress.org\u002Frioriost\u002F",2,0,100,30,94,"2026-08-29T11:20:34.918Z",[13,33],{"slug":14,"name":14,"version":15,"author":4,"author_profile":5,"description":16,"short_description":17,"active_installs":7,"downloaded":18,"rating":7,"num_ratings":7,"last_updated":19,"tested_up_to":20,"requires_at_least":21,"requires_php":22,"tags":23,"homepage":29,"download_link":30,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":31,"fetched_at":32},"affilun","0.9.3","\u003Cp>affilun is a WordPress plugin for managing affiliate product links used by Japanese websites. It stores products from Amazon Associates, Rakuten Ichiba, Yahoo! Shopping, Mercari, and other configured routes, then displays them as reusable product cards in posts.\u003C\u002Fp>\n\u003Cp>The local plugin features do not require a license key, trial, paid plan, or usage quota. Product storage, product cards, provider settings, and basic affiliate-link generation run within WordPress.\u003C\u002Fp>\n\u003Cp>You can optionally connect affilun Cloud for managed AI assistance, article drafting, link-health checks, campaign suggestions, affiliate-product suggestions, and plan information. These optional features are external SaaS services processed by affilun Cloud.\u003C\u002Fp>\n\u003Ch4>Main features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Store and manage affiliate product records in WordPress.\u003C\u002Fli>\n\u003Cli>Display product cards with a Gutenberg block or shortcode.\u003C\u002Fli>\n\u003Cli>Configure Amazon, Rakuten Ichiba, Yahoo! Shopping, Mercari, and ASP routing templates.\u003C\u002Fli>\n\u003Cli>Generate a standard Amazon product-detail URL with the configured Partner Tag when an ASIN is stored.\u003C\u002Fli>\n\u003Cli>Fetch discounted Amazon physical products daily and display priority brands before selected categories with a configurable shortcode.\u003C\u002Fli>\n\u003Cli>Store button labels, display templates, link attributes, and provider display settings in WordPress.\u003C\u002Fli>\n\u003Cli>Use optional Cloud features only when an affilun Cloud API key and eligible plan are configured.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>affilun Cloud boundary\u003C\u002Fh4>\n\u003Cp>The plugin distributed through WordPress.org is a GPL-licensed WordPress plugin. Local product management, product-card rendering, saved settings, and basic link generation run within WordPress.\u003C\u002Fp>\n\u003Cp>affilun Cloud is an optional external SaaS. Cloud features may include paid plans, usage limits, plan checks, Stripe Checkout, Cloud API-key issuance, AI assistance, article drafting, link-health checks, campaign suggestions, and affiliate-product suggestions. Local plugin features remain available without affilun Cloud.\u003C\u002Fp>\n\u003Cp>The affilun Cloud server implementation, billing system, hosted processing, and external API relay services are not included in this plugin package. See https:\u002F\u002Faffilun.st\u002F for Cloud terms, pricing, data retention, and deletion information.\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>affilun communicates with an external service only when the related feature is configured and used. Review each provider’s terms, privacy policy, and affiliate-program rules before enabling it.\u003C\u002Fp>\n\u003Ch4>Amazon Creators API \u002F Amazon Associates\u003C\u002Fh4>\n\u003Cp>Purpose: Amazon product search, product-data retrieval, daily brand- and category-based discount discovery, and Partner Tag link generation.\u003C\u002Fp>\n\u003Cp>Data sent when enabled: search terms and priority-brand filters when applicable, ASINs, discount categories and thresholds, marketplace, Creators API credentials, and Partner Tag.\u003C\u002Fp>\n\u003Cp>Terms: https:\u002F\u002Faffiliate-program.amazon.com\u002Fhelp\u002Foperating\u002Fagreement\u003C\u002Fp>\n\u003Cp>Privacy: https:\u002F\u002Fwww.amazon.com\u002Fgp\u002Fhelp\u002Fcustomer\u002Fdisplay.html?nodeId=468496\u003C\u002Fp>\n\u003Ch4>Rakuten Ichiba API\u003C\u002Fh4>\n\u003Cp>Purpose: Rakuten Ichiba product search, product-data retrieval, and affiliate-link generation.\u003C\u002Fp>\n\u003Cp>Data sent when enabled: search terms, item IDs, Application ID, Access Key, Affiliate ID, and the WordPress site’s Origin. The Access Key is sent in an HTTP header rather than the URL.\u003C\u002Fp>\n\u003Cp>Terms: https:\u002F\u002Fwebservice.rakuten.co.jp\u002Fguide\u002Frule\u003C\u002Fp>\n\u003Cp>Privacy: https:\u002F\u002Fprivacy.rakuten.co.jp\u002F\u003C\u002Fp>\n\u003Ch4>Yahoo! Shopping API and ValueCommerce routing\u003C\u002Fh4>\n\u003Cp>Purpose: Yahoo! Shopping product search, product-data retrieval, and link generation.\u003C\u002Fp>\n\u003Cp>Data sent when enabled: search terms, item IDs, Client ID, and related Yahoo! Shopping settings. If a ValueCommerce free-text-link HTML snippet is configured, affilun extracts and stores only the \u003Ccode>sid\u003C\u002Fcode> and \u003Ccode>pid\u003C\u002Fcode> values needed for link generation.\u003C\u002Fp>\n\u003Cp>Yahoo! JAPAN Developer Network guidelines: https:\u002F\u002Fdeveloper.yahoo.co.jp\u002Fguideline\u002F\u003C\u002Fp>\n\u003Cp>LY Corporation terms: https:\u002F\u002Fwww.lycorp.co.jp\u002Fen\u002Fcompany\u002Fterms\u002F\u003C\u002Fp>\n\u003Cp>LY Corporation privacy policy: https:\u002F\u002Fwww.lycorp.co.jp\u002Fen\u002Fcompany\u002Fprivacypolicy\u002F\u003C\u002Fp>\n\u003Cp>ValueCommerce terms: https:\u002F\u002Fwww.valuecommerce.ne.jp\u002Fst_affiliate\u002Fterms.html\u003C\u002Fp>\n\u003Cp>ValueCommerce privacy policy: https:\u002F\u002Fwww.valuecommerce.co.jp\u002Fprivacy_policy\u002F\u003C\u002Fp>\n\u003Ch4>Mercari\u003C\u002Fh4>\n\u003Cp>Purpose: Generate Mercari search or product links containing a configured Mercari Ambassador \u003Ccode>afid\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Data sent when enabled: search terms, Mercari URLs, and \u003Ccode>afid\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Visitor browser requests: when a saved Mercari product has no main image URL, a product card may load a Mercari Ambassador image from \u003Ccode>ambassador-system.mercari.com\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Terms: https:\u002F\u002Fstatic.jp.mercari.com\u002Ftos\u003C\u002Fp>\n\u003Cp>Privacy: https:\u002F\u002Fstatic.jp.mercari.com\u002Fprivacy\u003C\u002Fp>\n\u003Ch4>affilun Cloud\u003C\u002Fh4>\n\u003Cp>Purpose: optional managed AI assistance, product-keyword normalization, article drafting, campaign suggestions, revenue-opportunity suggestions, affiliate-product suggestions, Amazon category discount listings, link-health checks, plan checks, Cloud API-key validation, and usage reporting.\u003C\u002Fp>\n\u003Cp>Service endpoint: affilun Cloud uses \u003Ccode>https:\u002F\u002Fapi.affilun.st\u002Fapi\u002Fv1\u003C\u002Fcode>. Legacy saved endpoints at \u003Ccode>https:\u002F\u002Fcbl.rio.st\u003C\u002Fcode> are normalized to the production affilun Cloud endpoint.\u003C\u002Fp>\n\u003Cp>Data sent when configured and used: site URL, site name, administrator email address, Cloud API key, plan context, enabled provider keys, selected Amazon category, post excerpts or content needed for the selected operation, product-link metadata, review-source URLs, and link-health inputs.\u003C\u002Fp>\n\u003Cp>The Free state is for connection checks. Managed Cloud features may require a paid plan or Stripe trial because processing occurs on affilun Cloud servers.\u003C\u002Fp>\n\u003Cp>Terms: https:\u002F\u002Faffilun.st\u002Fcloud-subscription-terms\u002F\u003C\u002Fp>\n\u003Cp>Privacy: https:\u002F\u002Faffilun.st\u002Fprivacy\u002F\u003C\u002Fp>\n\u003Ch4>Stripe Checkout\u003C\u002Fh4>\n\u003Cp>Purpose: payment flow for affilun Cloud plans.\u003C\u002Fp>\n\u003Cp>Data sent when an administrator starts checkout: email address, site information, selected plan, and checkout-session information.\u003C\u002Fp>\n\u003Cp>Terms: https:\u002F\u002Fstripe.com\u002Flegal\u002Fssa\u003C\u002Fp>\n\u003Cp>Privacy: https:\u002F\u002Fstripe.com\u002Fprivacy\u003C\u002Fp>\n\u003Ch4>External product images\u003C\u002Fh4>\n\u003Cp>Product cards and administration previews may display product-image URLs saved in WordPress. These URLs may point to provider, marketplace, affiliate-network, or CDN domains. When a page containing an external image is viewed, the visitor’s browser sends a request to that domain, which may receive the visitor’s IP address, user agent, referrer, and other request information.\u003C\u002Fp>\n\u003Ch4>Data stored in WordPress\u003C\u002Fh4>\n\u003Cp>affilun may store:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Provider settings, including Amazon credentials and Partner Tag, Rakuten credentials, Yahoo! credentials, Mercari \u003Ccode>afid\u003C\u002Fcode>, and enabled states.\u003C\u002Fli>\n\u003Cli>Product records, including title, provider item ID, ASIN, price, availability, image URL, product URL, affiliate URL, synchronization state, and timestamps.\u003C\u002Fli>\n\u003Cli>Daily Amazon discount snapshots stored separately from manually managed affiliate products.\u003C\u002Fli>\n\u003Cli>Priority-brand names configured for Amazon discount synchronization and shortcode display.\u003C\u002Fli>\n\u003Cli>Display settings, including templates, button labels, link attributes, and display options.\u003C\u002Fli>\n\u003Cli>ASP routing settings and URL templates.\u003C\u002Fli>\n\u003Cli>affilun Cloud settings, including Cloud API key, site ID, endpoint, selected plan, and connection state.\u003C\u002Fli>\n\u003Cli>Operational data, including logs, sync jobs, audit events, link-health results, opportunity states, cached affiliate suggestions, local click events, and daily click\u002Fview aggregates.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>API keys and affiliate identifiers are stored in the WordPress database and managed by administrators. They are not rendered on public pages.\u003C\u002Fp>\n\u003Ch3>ASP Routing\u003C\u002Fh3>\n\u003Cp>Yahoo! Shopping affiliate tracking is configured with a Yahoo Developer Client ID and a ValueCommerce free-text-link HTML snippet. affilun extracts and stores only the \u003Ccode>sid\u003C\u002Fcode> and \u003Ccode>pid\u003C\u002Fcode> values needed for link generation.\u003C\u002Fp>\n\u003Cp>Advanced routing templates can also be configured for custom ASPs or migrations. Templates may use placeholders such as \u003Ccode>{url}\u003C\u002Fcode>, \u003Ccode>{encoded_url}\u003C\u002Fcode>, \u003Ccode>{provider}\u003C\u002Fcode>, and \u003Ccode>{product_id}\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>When routing is enabled, a product-button URL may be transformed into the configured intermediary ASP URL. The site operator is responsible for confirming that each template complies with the relevant ASP rules and tracking requirements.\u003C\u002Fp>\n\u003Ch3>Uninstall\u003C\u002Fh3>\n\u003Cp>Deleting the plugin through WordPress runs \u003Ccode>uninstall.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>The current uninstall policy removes secrets and operational options, including provider credentials, the affilun Cloud API key and connection settings, local click aggregate options, cron cursors, worker IDs, and scheduled affilun cron hooks.\u003C\u002Fp>\n\u003Cp>Custom tables containing products, logs, audits, synchronization data, link-health data, analytics, and click aggregates are retained unless an explicit data-removal option is introduced in a future release. Back up required data before deleting the plugin.\u003C\u002Fp>\n","Manage reusable affiliate product links and product cards for Amazon, Rakuten, Yahoo! Shopping, and Mercari.",339,"2026-07-17T11:48:00.000Z","7.0.2","6.6","8.1",[24,25,26,27,28],"affiliate","amazon","product-card","product-links","rakuten","https:\u002F\u002Faffilun.st\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Faffilun.0.9.3.zip",null,"2026-07-22T17:31:50.256Z",{"slug":34,"name":35,"version":36,"author":4,"author_profile":5,"description":37,"short_description":38,"active_installs":7,"downloaded":39,"rating":7,"num_ratings":7,"last_updated":40,"tested_up_to":20,"requires_at_least":21,"requires_php":22,"tags":41,"homepage":47,"download_link":48,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":31,"fetched_at":32},"ritriever","RiTriever","0.2.3","\u003Cp>RiTriever adds RAG-style vector retrieval to WordPress search. Published content is embedded, stored in a local vector table, and blended with standard WordPress search results.\u003C\u002Fp>\n\u003Cp>The plugin is intended for WordPress sites that can use native database vector support, primarily MariaDB 11.7 or later. It can index posts, pages, and configured public post types, then use those vectors during front-end search.\u003C\u002Fp>\n\u003Cp>Main features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>RAG-style search blending with standard WordPress search.\u003C\u002Fli>\n\u003Cli>Native vector storage in the WordPress database.\u003C\u002Fli>\n\u003Cli>OpenAI and Azure OpenAI support for external embedding APIs.\u003C\u002Fli>\n\u003Cli>Local or self-hosted embedding support through Ollama, LM Studio, Infinity, TEI, or Custom HTTP endpoints.\u003C\u002Fli>\n\u003Cli>RAG target language selection from WordPress-supported locales.\u003C\u002Fli>\n\u003Cli>Admin diagnostics for database support, embedding providers, indexing progress, and live vector queries.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>External API use is optional. WordPress 7.0 AI Client does not provide embedding generation, so RiTriever uses direct embedding APIs when external embeddings are configured. Post content and configured custom field values are sent to the selected provider to create embeddings.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>RiTriever connects to external services only when you select an external embedding provider. It sends post titles, post excerpts, post content chunks, selected taxonomy terms, selected custom field values, and short admin test strings when indexing or testing embeddings. The vectors returned by the provider are stored in your WordPress database.\u003C\u002Fp>\n\u003Cp>WordPress 7.0 includes the WordPress AI Client for supported AI capabilities, but the current AI Client announcement and implementation do not include an embeddings API. Because RiTriever requires text embeddings for vector search, it calls embedding providers directly instead of using WordPress AI Client. Reference: https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2026\u002F03\u002F24\u002Fintroducing-the-ai-client-in-wordpress-7-0\u002F\u003C\u002Fp>\n\u003Cp>OpenAI sends embedding requests to OpenAI for \u003Ccode>text-embedding-3-small\u003C\u002Fcode> or \u003Ccode>text-embedding-3-large\u003C\u002Fcode>. This service is provided by OpenAI: Terms of use https:\u002F\u002Fopenai.com\u002Fpolicies\u002Fterms-of-use\u002F and Privacy policy https:\u002F\u002Fopenai.com\u002Fpolicies\u002Fprivacy-policy\u002F.\u003C\u002Fp>\n\u003Cp>Azure OpenAI sends embedding requests to your configured Azure OpenAI endpoint. This service is provided by Microsoft Azure: Terms of use https:\u002F\u002Fwww.microsoft.com\u002Flicensing\u002Fterms\u002Fproductoffering\u002FMicrosoftAzure\u002FMCA and Privacy statement https:\u002F\u002Fprivacy.microsoft.com\u002Fprivacystatement.\u003C\u002Fp>\n\u003Cp>Local or self-hosted endpoints, including Ollama, LM Studio, Infinity, TEI, and Custom HTTP, receive the same embedding inputs when selected. Review the terms, privacy policy, and network location for the endpoint you operate or configure.\u003C\u002Fp>\n","Adds RAG-style vector retrieval to WordPress search using native database vector indexes and configurable embeddings.",70,"2026-07-03T12:35:00.000Z",[42,43,44,45,46],"embeddings","rag","search","semantic-search","vector-search","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fritriever.0.2.3.zip"]