[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fKI9tJxtbN0hQ2tNDtZT4sTkopoSwADHPrLblQyQq6WA":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},"wpvoicer","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpvoicer\u002F",2,0,100,30,94,"2026-08-28T23:30:57.571Z",[13,34],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":7,"num_ratings":7,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"sibillo-audio","Sibillo Audio – Text to Speech, AI Voices & Podcast Feeds","2.6.7","\u003Cp>Sibillo Audio turns your WordPress posts into natural-sounding audio, so visitors can listen to your articles instead of reading them. Speech is generated in the cloud by the external WPVoicer.com text-to-speech service: an administrator explicitly selects a post and requests generation, and the completed MP3 is downloaded to the site’s WordPress Media Library.\u003C\u002Fp>\n\u003Cp>The plugin also provides local features that remain available when the WPVoicer.com account is disconnected:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Audio Library for previously generated MP3 files\u003C\u002Fli>\n\u003Cli>Local audio playback and play counts\u003C\u002Fli>\n\u003Cli>Shortcode and page-builder audio fields\u003C\u002Fli>\n\u003Cli>Podcast management and locally generated RSS feeds\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Generate speech from WordPress post content\u003C\u002Fli>\n\u003Cli>Select languages and standard or premium cloud voices\u003C\u002Fli>\n\u003Cli>Upload a voice sample when voice cloning is enabled for the connected service account\u003C\u002Fli>\n\u003Cli>Store generated MP3 files in the WordPress Media Library\u003C\u002Fli>\n\u003Cli>Embed audio with \u003Ccode>[sibillo_audio_audio]\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Use audio fields with Elementor, Bricks, and Breakdance\u003C\u002Fli>\n\u003Cli>Build podcast feeds from posts that already contain generated audio\u003C\u002Fli>\n\u003Cli>Manage local audio and podcast feeds while disconnected\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>External service and pricing\u003C\u002Fh4>\n\u003Cp>Cloud generation requires a WPVoicer.com account and available service credits or an eligible service plan. Introductory credits may be included with a new service account. Additional credits and cloud capabilities are offered by WPVoicer.com.\u003C\u002Fp>\n\u003Cp>The WordPress plugin code is free and fully available under the GPL. Payment applies only to cloud processing and service capacity supplied by WPVoicer.com. The plugin does not download premium code or executable updates from the service. Existing local MP3 files, playback, Audio Library and podcast features are not removed when cloud generation is unavailable.\u003C\u002Fp>\n\u003Ch4>How it works\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Install and activate Sibillo Audio.\u003C\u002Fli>\n\u003Cli>Open Sibillo Audio > Connection and connect a WPVoicer.com account.\u003C\u002Fli>\n\u003Cli>Configure a voice under Voice Settings.\u003C\u002Fli>\n\u003Cli>Edit a post and explicitly request audio generation.\u003C\u002Fli>\n\u003Cli>The post content and selected settings are sent to WPVoicer.com.\u003C\u002Fli>\n\u003Cli>The generated MP3 is downloaded to the site’s Media Library.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Third Party Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the external WPVoicer.com Software-as-a-Service platform. The service performs text-to-speech generation, voice previews, speaker-list retrieval, account and usage requests, and custom voice processing.\u003C\u002Fp>\n\u003Cp>The plugin does not contact WPVoicer.com merely because it is installed, activated, deactivated, or loaded. Requests are made when an administrator performs an action that requires the service, including registration, login, loading service voice data, previewing a voice, checking account usage, uploading or deleting a custom voice sample, generating audio, polling a requested job, downloading generated audio, or opening an authenticated dashboard link.\u003C\u002Fp>\n\u003Ch4>Data sent to WPVoicer.com\u003C\u002Fh4>\n\u003Cp>Depending on the requested action, the plugin may send:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Account credentials or connection data entered by the administrator\u003C\u002Fli>\n\u003Cli>Site URL and site identifier used to associate the connection\u003C\u002Fli>\n\u003Cli>Selected post ID, title and text for requested speech generation\u003C\u002Fli>\n\u003Cli>Language, voice, provider, speed and generation parameters\u003C\u002Fli>\n\u003Cli>A custom voice sample when the administrator explicitly uploads one\u003C\u002Fli>\n\u003Cli>Job identifiers used to retrieve generation status and audio\u003C\u002Fli>\n\u003Cli>Plugin, WordPress and PHP versions as part of authenticated service requests\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Local data\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Generated MP3 files are downloaded to the site’s Media Library.\u003C\u002Fli>\n\u003Cli>Audio references, settings and play counts are stored in WordPress options or post metadata.\u003C\u002Fli>\n\u003Cli>Podcast RSS feeds are generated locally from WordPress posts and local audio.\u003C\u002Fli>\n\u003Cli>Existing local audio and podcast functionality remains available after disconnection.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Service links\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Service: https:\u002F\u002Fwww.wpvoicer.com\u002F\u003C\u002Fli>\n\u003Cli>Terms of Service: https:\u002F\u002Fwww.wpvoicer.com\u002Fterms\u002F\u003C\u002Fli>\n\u003Cli>Privacy Policy: https:\u002F\u002Fwww.wpvoicer.com\u002Fprivacy-policy\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>All service requests use HTTPS and the WordPress HTTP API.\u003C\u002Fp>\n","Text to speech for WordPress: turn posts into audio with AI voices via the WPVoicer.com cloud service, and publish podcast RSS feeds.",172,"2026-06-20T12:32:00.000Z","7.0.2","5.9","8.0",[25,26,27,28,29],"accessibility","audio","podcast","text-to-speech","tts","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsibillo-audio.2.6.7.zip",null,"2026-07-22T17:31:50.256Z",{"slug":35,"name":36,"version":37,"author":4,"author_profile":5,"description":38,"short_description":39,"active_installs":7,"downloaded":40,"rating":7,"num_ratings":7,"last_updated":41,"tested_up_to":21,"requires_at_least":42,"requires_php":43,"tags":44,"homepage":50,"download_link":51,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"spawnwp-deploy","SpawnWP Deploy","0.3.4","\u003Cp>SpawnWP Deploy provides two administrator-initiated workflows:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Capture a configured WordPress site as a reusable blueprint on a self-hosted SpawnWP server.\u003C\u002Fli>\n\u003Cli>Publish a finished site once to a separate, fresh WordPress installation.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It is not a continuous staging or synchronization system. Site-to-site deployment is\u003Cbr \u002F>\nlimited to an empty destination and keeps rollback data for seven days. Connections use\u003Cbr \u002F>\nsingle-use pairing codes, signed requests and replay protection.\u003C\u002Fp>\n\u003Cp>For blueprint capture, the administrator chooses whether to include plugins, themes,\u003Cbr \u002F>\nuploads and database content. WordPress users and user metadata are excluded. The source\u003Cbr \u002F>\nsite URL is replaced with a fixed placeholder in captured database content, and each site\u003Cbr \u002F>\ncreated from the blueprint receives its own administrator credentials.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress single-site.\u003C\u002Fli>\n\u003Cli>PHP 7.4 or later with the Sodium and ZIP extensions.\u003C\u002Fli>\n\u003Cli>HTTPS with a publicly trusted certificate on paired endpoints.\u003C\u002Fli>\n\u003Cli>A reachable WordPress REST API without an additional HTTP password.\u003C\u002Fli>\n\u003Cli>Write access to the WordPress plugin, theme and uploads directories.\u003C\u002Fli>\n\u003Cli>Sufficient free disk space for staging and rollback data.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Always back up important sites before using deployment or capture tools.\u003C\u002Fp>\n\u003Ch3>External Connections\u003C\u002Fh3>\n\u003Cp>This plugin does not contact a SpawnWP-operated SaaS platform and does not send telemetry\u003Cbr \u002F>\nto SpawnWP merely because it is installed, activated or loaded.\u003C\u002Fp>\n\u003Cp>An administrator can explicitly pair the plugin with either:\u003C\u002Fp>\n\u003Col>\n\u003Cli>another WordPress site running SpawnWP Deploy; or\u003C\u002Fli>\n\u003Cli>a self-hosted SpawnWP server whose URL is supplied by the administrator.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>During a requested deployment or capture, the plugin sends the selected package and\u003Cbr \u002F>\ntechnical metadata to that administrator-selected endpoint. Depending on the selected\u003Cbr \u002F>\noptions, this can include plugin and theme files, media uploads, database content,\u003Cbr \u002F>\nWordPress and PHP versions, plugin names and versions, package checksums, job identifiers\u003Cbr \u002F>\nand connection signatures. WordPress user and user-meta tables are excluded.\u003C\u002Fp>\n\u003Cp>The remote endpoint is operated by the site administrator or their chosen provider. Its\u003Cbr \u002F>\nprivacy and retention practices are therefore controlled by that operator. SpawnWP is\u003Cbr \u002F>\nself-hosted open-source software distributed under the MIT License:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>SpawnWP project: https:\u002F\u002Fspawnwp.com\u002F\u003C\u002Fli>\n\u003Cli>Source code and license: https:\u002F\u002Fgithub.com\u002Ftts-empire\u002Fspawnwp\u003C\u002Fli>\n\u003Cli>Security documentation: https:\u002F\u002Fspawnwp.com\u002Fdocs\u002Fsecurity\u002F\u003C\u002Fli>\n\u003Cli>Optional SpawnWP platform telemetry notice: https:\u002F\u002Fspawnwp.com\u002Fprivacy\u002Ftelemetry\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When the plugin inventory is displayed and WordPress does not already have cached update\u003Cbr \u002F>\ninformation for an active plugin, SpawnWP Deploy may query the WordPress.org Plugins API\u003Cbr \u002F>\nusing WordPress core’s \u003Ccode>plugins_api()\u003C\u002Fcode> function. It sends the plugin slug and uses the\u003Cbr \u002F>\nresponse only to classify the plugin as WordPress.org-hosted or custom. The result is\u003Cbr \u002F>\ncached for one day. WordPress.org privacy policy: https:\u002F\u002Fwordpress.org\u002Fabout\u002Fprivacy\u002F\u003C\u002Fp>\n","Capture a configured site as a reusable blueprint, or publish it once to a separate empty WordPress installation.",125,"2026-07-20T09:33:00.000Z","6.8","7.4",[45,46,47,48,49],"blueprint","deployment","development","migration","staging","https:\u002F\u002Fspawnwp.com\u002Fdocs\u002Fwordpress-development\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fspawnwp-deploy.0.3.4.zip"]