[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fGdvyzWtkUezsyZMa4CTWRFcjr7NRPfnWt8jNgNPhNq8":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"presents111","miya","https:\u002F\u002Fprofiles.wordpress.org\u002Fpresents111\u002F",2,0,100,30,94,"2026-08-29T14:58:17.815Z",[14,35],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":8,"downloaded":20,"rating":8,"num_ratings":8,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":9,"vuln_count":8,"unpatched_count":8,"last_vuln_date":33,"fetched_at":34},"kagivault","Kagivault","0.1.2","\u003Cp>Kagivault is an encrypted vault for the \u003Cstrong>WordPress 7.0 AI Connectors API\u003C\u002Fstrong>. Out of the box, WordPress stores the API keys you configure on \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Connectors\u003C\u002Fstrong> (OpenAI, Anthropic, Google, OpenRouter, and any other AI provider registered with the AI Client) as plaintext rows in the \u003Ccode>wp_options\u003C\u002Fcode> table. Anyone with database access — backups, leaked dumps, host migration files — can read them.\u003C\u002Fp>\n\u003Cp>Kagivault wraps each AI Connectors key with \u003Cstrong>XChaCha20-Poly1305 (authenticated encryption)\u003C\u002Fstrong> and protects the data-encryption key with a \u003Cstrong>vault password derived through Argon2id\u003C\u002Fstrong>. The vault password is never persisted, and the vault automatically re-locks after a short, configurable idle timeout. Unlock from the admin UI, and the WordPress AI client transparently sees the decrypted keys — no other plugin changes required.\u003C\u002Fp>\n\u003Ch4>Highlights\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Drop-in encryption for every AI Connectors provider (\u003Ccode>connectors_ai_*_api_key\u003C\u002Fcode> rows)\u003C\u002Fli>\n\u003Cli>Vault password unlock with idle-timeout auto-lock\u003C\u002Fli>\n\u003Cli>Recovery key as a parallel unlock path\u003C\u002Fli>\n\u003Cli>Optional: link a WordPress login password so signing in automatically unlocks the vault\u003C\u002Fli>\n\u003Cli>Easy-mode initialization — no separate vault password to remember if you just want one-click setup\u003C\u002Fli>\n\u003Cli>Transparent for the core WP AI client and the Connectors admin page\u003C\u002Fli>\n\u003Cli>Versioned blob format for future cipher upgrades\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 7.0 or newer (uses the Connectors API introduced in 7.0)\u003C\u002Fli>\n\u003Cli>PHP 8.3 or newer\u003C\u002Fli>\n\u003Cli>PHP sodium extension with \u003Cstrong>XChaCha20-Poly1305 AEAD\u003C\u002Fstrong> (\u003Ccode>sodium_crypto_aead_xchacha20poly1305_ietf_encrypt\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>PHP sodium extension with \u003Cstrong>Argon2id\u003C\u002Fstrong> (\u003Ccode>SODIUM_CRYPTO_PWHASH_ALG_ARGON2ID13\u003C\u002Fcode>, requires libsodium 1.0.13+)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The bundled sodium extension shipped with PHP 8.3+ on most platforms (Debian\u002FUbuntu \u003Ccode>php-sodium\u003C\u002Fcode>, RHEL \u003Ccode>php-sodium\u003C\u002Fcode>, Alpine \u003Ccode>php-sodium\u003C\u002Fcode>, Windows official builds) includes both capabilities. The plugin refuses to activate and surfaces a clear admin notice if either is unavailable.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>Kagivault does NOT:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Send any data to external servers\u003C\u002Fli>\n\u003Cli>Track users\u003C\u002Fli>\n\u003Cli>Use cookies for tracking\u003C\u002Fli>\n\u003Cli>Share data with third parties\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Kagivault DOES:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Process and store encrypted API keys locally on your server (\u003Ccode>wp_options\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Keep the data-encryption key only in a short-lived transient that expires after the configured idle timeout\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For support, bug reports, or feature requests:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Website: https:\u002F\u002Fgithub.com\u002Fbenridane\u002Fkagivault\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development happens on GitHub. Pull requests welcome!\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Follow WordPress coding standards\u003C\u002Fli>\n\u003Cli>All code must pass \u003Ccode>wp plugin check kagivault\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n","Encrypts WordPress AI Connectors API keys (OpenAI, Anthropic, Google, OpenRouter) at rest with XChaCha20-Poly1305 + Argon2id.",154,"2026-06-06T11:54:00.000Z","7.0.2","7.0","8.3",[26,27,28,29,30],"ai","ai-connectors","api-keys","connectors","encryption","https:\u002F\u002Fgithub.com\u002Fbenridane\u002Fkagivault","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkagivault.0.1.2.zip",null,"2026-07-22T17:31:50.256Z",{"slug":36,"name":37,"version":38,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":8,"downloaded":41,"rating":8,"num_ratings":8,"last_updated":42,"tested_up_to":22,"requires_at_least":43,"requires_php":44,"tags":45,"homepage":51,"download_link":52,"security_score":9,"vuln_count":8,"unpatched_count":8,"last_vuln_date":33,"fetched_at":34},"piip-pii-protection","PIIP – PII Protection","1.6.0","\u003Cp>PIIP (PII Protection) is a plugin that automatically detects and masks personally identifiable information (PII) in WordPress comments and community plugin content before the data is saved to your database. This helps protect user privacy and supports your compliance efforts under privacy regulations such as the GDPR. Note that PIIP is a technical tool and does not by itself make your site GDPR compliant.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automatic PII Detection\u003C\u002Fstrong>: Intelligently detects multiple types of PII including emails, phone numbers, addresses, credit cards, SSN\u002FMy Number, passwords, API tokens, IP addresses, and hosting account IDs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Server-Side Masking\u003C\u002Fstrong>: All masking happens on the server (PHP) for maximum security – cannot be bypassed by users\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WordPress Core Support\u003C\u002Fstrong>: Native support for WordPress comments\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Community Plugin Support\u003C\u002Fstrong>: Works seamlessly with wpForo, BuddyPress, bbPress, and other popular community plugins\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Configurable\u003C\u002Fstrong>: Choose which PII types to mask via easy-to-use settings page\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Consent Opt-Out\u003C\u002Fstrong>: Users can include consent phrases to skip masking when sharing personal info publicly\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Presidio-Level Detection\u003C\u002Fstrong>: High-accuracy detection with validation (Luhn for credit cards, check digits for My Number)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retroactive Scan\u003C\u002Fstrong>: Scan content that existed before installing PIIP and apply masking after a dry-run review\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Patterns\u003C\u002Fstrong>: Mask site-specific identifiers (employee IDs, member numbers) with your own regular expressions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP-CLI Support\u003C\u002Fstrong>: \u003Ccode>wp piip mask\u003C\u002Fcode> and \u003Ccode>wp piip scan\u003C\u002Fcode> commands for automation and large sites\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Supported PII Types\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Email addresses (example@domain.com \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> e***@domain.com)\u003C\u002Fli>\n\u003Cli>Phone numbers (Japanese mobile\u002Flandline, international formats)\u003C\u002Fli>\n\u003Cli>Japanese street addresses in free text (東京都新宿区西新宿2-8-1 \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> 東京都\u003Cstrong>\u003Cem>) and labeled postal codes (〒123-4567 \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> 〒\u003C\u002Fem>\u003C\u002Fstrong>-****)\u003C\u002Fli>\n\u003Cli>Credit card numbers with Luhn validation (4532-1234-5678-9010 \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> ****-****-****-9010)\u003C\u002Fli>\n\u003Cli>Social Security Numbers \u002F Japanese My Number with check digit validation\u003C\u002Fli>\n\u003Cli>Passwords, including labeled values in free text (password: xxx \u002F パスワードは xxx \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> [REDACTED])\u003C\u002Fli>\n\u003Cli>HTTP credentials: Basic auth (curl -u, Authorization: Basic, user:pass@host URLs) and Bearer tokens (including JWTs)\u003C\u002Fli>\n\u003Cli>Developer secrets: GitHub, Slack, AWS, Stripe tokens and SSH\u002FPEM private key blocks\u003C\u002Fli>\n\u003Cli>API Tokens\u002FKeys (partial masking showing first and last 4 characters)\u003C\u002Fli>\n\u003Cli>AI API Keys (OpenAI sk-***, Anthropic sk-ant-***, Google AIza***, Hugging Face hf_***, Replicate r8_***, Cohere, Azure OpenAI)\u003C\u002Fli>\n\u003Cli>Labeled dates of birth (生年月日: 1990-01-15 \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> ****-\u003Cstrong>–\u003C\u002Fstrong>)\u003C\u002Fli>\n\u003Cli>Labeled bank account numbers (口座番号: 1234567 \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> ***4567)\u003C\u002Fli>\n\u003Cli>Names in self-introduction phrases (山田太郎と申します \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> 山***と申します; opt-in, off by default)\u003C\u002Fli>\n\u003Cli>IP Addresses (192.168.1.1 \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> 192.\u003Cstrong>\u003Cem>.\u003C\u002Fem>\u003C\u002Fstrong>1)\u003C\u002Fli>\n\u003Cli>Hosting Account IDs (XServer, Sakura, AWS, Azure, GCP, ConoHa, Lolipop, mixhost)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Supported Integrations\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WordPress Core\u003C\u002Fstrong>\n\u003Cul>\n\u003Cli>Comments\u003C\u002Fli>\n\u003Cli>User Profiles (display name, nickname, biographical info)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Form Plugins\u003C\u002Fstrong>\n\u003Cul>\n\u003Cli>Contact Form 7 (free-text fields; protects sent mail and stored copies such as Flamingo)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Community Plugins\u003C\u002Fstrong>\n\u003Cul>\n\u003Cli>wpForo Forum\u003C\u002Fli>\n\u003Cli>BuddyPress\u003C\u002Fli>\n\u003Cli>bbPress\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>More integrations coming soon!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Col>\n\u003Cli>User posts a comment or content in a community plugin\u003C\u002Fli>\n\u003Cli>PIIP intercepts the submission before database save\u003C\u002Fli>\n\u003Cli>Automatically detects PII using field names, regex patterns, and validation\u003C\u002Fli>\n\u003Cli>Masks detected PII according to your settings\u003C\u002Fli>\n\u003Cli>Content saves normally with masked data\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Privacy & Security\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>All processing happens on YOUR server (no external API calls)\u003C\u002Fli>\n\u003Cli>Original values are NEVER stored for maximum privacy protection\u003C\u002Fli>\n\u003Cli>Server-side processing prevents client-side bypass attempts\u003C\u002Fli>\n\u003Cli>Full control over your data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>PIIP – PII Protection does NOT:\u003Cbr \u002F>\n* Send any data to external servers\u003Cbr \u002F>\n* Track users\u003Cbr \u002F>\n* Use cookies\u003Cbr \u002F>\n* Share data with third parties\u003C\u002Fp>\n\u003Cp>PIIP DOES:\u003Cbr \u002F>\n* Process content locally on your server\u003Cbr \u002F>\n* Automatically mask PII without storing sensitive data\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For support, bug reports, or feature requests:\u003Cbr \u002F>\n* Website: https:\u002F\u002Fgithub.com\u002Fbenridane\u002Fpiip\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development happens on GitHub. Pull requests welcome!\u003Cbr \u002F>\n* Follow coding standards\u003Cbr \u002F>\n* All code must pass \u003Ccode>composer run phpcs\u003C\u002Fcode>\u003C\u002Fp>\n","Automatically detects and masks PII in WordPress comments and forms to protect user privacy and support your GDPR compliance efforts.",503,"2026-07-06T12:41:00.000Z","6.9","8.2",[46,47,48,49,50],"data-protection","gdpr","pii","privacy","security","https:\u002F\u002Fbenridane.com\u002Fpiip","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpiip-pii-protection.1.6.0.zip"]