Setup Wizard, admin\u2011post redirect fix to avoid header warnings, and UX improvements.<\/p>","1.0.0":"
Kararl\u0131 ilk s\u00fcr\u00fcm.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3377206,"resolution":"128x128","location":"assets","locale":""},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3377206,"resolution":"256x256","location":"assets","locale":""}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1","1.0.2"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Dashboard overview and insights","2":"Logs with filters","3":"Badge examples"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[11155,157415,396,600,1917],"plugin_category":[54],"plugin_contributors":[249075],"plugin_business_model":[],"class_list":["post-253031","plugin","type-plugin","status-publish","hentry","plugin_tags-breach","plugin_tags-data-breach","plugin_tags-privacy","plugin_tags-security","plugin_tags-users","plugin_category-security-and-spam-protection","plugin_contributors-verisizintisi","plugin_committers-verisizintisi"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/breach-radar\/assets\/icon-128x128.png?rev=3377206","icon_2x":"https:\/\/ps.w.org\/breach-radar\/assets\/icon-256x256.png?rev=3377206","generated":false},"screenshots":[],"raw_content":"\n
Breach Radar helps WordPress site owners monitor whether their users\u2019 email addresses appear in known data breaches.<\/p>\n\n
Features:\n- Dashboard overview with risk summary and insights\n- Manual and scheduled scans (daily)\n- Logs with filters (email, found, HTTP, date range)\n- Admin notifications on breach count increases (configurable threshold)\n- Protection badge shortcode and Theme Customizer integration\n- i18n: English and Turkish included; Azerbaijani and Russian supported via PO files<\/p>\n\n
wordpress\/languages\/<\/code>.<\/li>\n- Plugin UI language can be forced at Breach Radar \u2192 Settings \u2192 Language. Default is \u201cAuto (Site language)\u201d.<\/li>\n
- Language: English | T\u00fcrk\u00e7e \u2192 readme-tr_TR.txt<\/li>\n<\/ul>\n\n
Data sent to the service<\/h4>\n\n\n- Site domain (host) to validate token usage<\/li>\n
- The email addresses you submit for lookup (transmitted for lookup; not persisted by the API)<\/li>\n
- Usage metadata (request time, status code, counters) for rate\u2011limiting and abuse prevention<\/li>\n<\/ul>\n\n
Privacy and Terms<\/h4>\n\n\n- No tracking scripts are added to your WordPress frontend or admin.<\/li>\n
- Lookups only run when you initiate them or via your scheduled task. Visitors are not tracked.<\/li>\n
- Review: https:\/\/verisizintisi.com\/privacy and https:\/\/verisizintisi.com\/terms<\/li>\n<\/ul>\n\n
Security model<\/h4>\n\n\n- Admin pages require
manage_options<\/code> capability.<\/li>\n- All state\u2011changing actions use nonces (
check_admin_referer<\/code>).<\/li>\n- Inputs sanitized and validated; outputs escaped (
esc_html<\/code>, esc_attr<\/code>, esc_url<\/code>, wp_kses_post<\/code>).<\/li>\n- HTTP host is derived via a safe helper instead of raw
$_SERVER<\/code>.<\/li>\n<\/ul>\n\nConsent<\/h4>\n\n
Depending on your local laws and policies, you may need to inform users and\/or obtain consent before checking their email addresses against breach datasets. This plugin provides the tools, but responsibility for lawful use remains with the site owner.<\/p>\n\n\n
From your WordPress admin:\n1. Plugins \u2192 Add New \u2192 Upload Plugin \u2192 select the ZIP \u2192 Install Now \u2192 Activate\n2. Get your API key at get.verisizintisi.com\/wordpress\n3. Go to Breach Radar \u2192 Settings and paste your API key\n4. (Optional) Configure scan filters, notifications, language\n5. Start a manual scan or enable daily scans<\/p>\n\n\n
\nDoes this show breach contents inside WordPress?<\/h3><\/dt>\nNo. Breach contents are user\u2011private on verisizintisi.com. Admins see presence and counts only.<\/p><\/dd>\n
Does the API store my users\u2019 emails?<\/h3><\/dt>\nEmails are transmitted for lookup and not stored in usage logs. The service records minimal metadata for rate\u2011limiting and abuse prevention.<\/p><\/dd>\n
How often can I call the API?<\/h3><\/dt>\nDefault daily limit is 10 requests per token (subject to change by plan). See the dashboard usage card.<\/p><\/dd>\n
How do I add the protection badge?<\/h3><\/dt>\nUse the shortcode:\n[verisizintisi_badge size=\"medium\" theme=\"light\" align=\"left\" lang=\"auto\"]\nOr use Appearance \u2192 Customize \u2192 Breach Radar Badge.<\/p><\/dd>\n
Can I force the plugin language?<\/h3><\/dt>\nYes. Go to Breach Radar \u2192 Settings \u2192 Language. \u201cAuto\u201d follows the site language. You can force Turkish, English, Azerbaijani, or Russian.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.2<\/h4>\n\n\n- Added first\u2011run Setup Wizard (activation redirect, two\u2011step flow)<\/li>\n
- API key connectivity test with clear status; daily scan toggle<\/li>\n
- Admin notice until setup is completed<\/li>\n
- Fixed redirects by processing setup via admin\u2011post to avoid \"headers already sent\"<\/li>\n
- Minor UX copy and layout improvements<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Compliance and security improvements for Plugin Check<\/li>\n
- Replaced raw $_SERVER usage with safe
get_site_url_safe()<\/code><\/li>\n- Escaped flagged outputs (esc_html\/esc_attr\/esc_url\/wp_kses_post)<\/li>\n
- Confirmed sanitization\/validation of GET\/POST data<\/li>\n
- Self\u2011healing scheduling for daily scans and last run tracking<\/li>\n
- rand() \u2192 wp_rand(); parse_url() \u2192 wp_parse_url(); date() \u2192 gmdate()<\/li>\n
- Always use $wpdb->prepare() with placeholders in Logs queries<\/li>\n
- i18n fixes (Text Domain breach-radar), updated POT\/PO files<\/li>\n
- Removed chart embeds and unused assets<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- \u0130lk kararl\u0131 s\u00fcr\u00fcm: risk \u00f6zeti, \u00f6ng\u00f6r\u00fcler, g\u00fcnl\u00fck tarama, kay\u0131t filtreleri, bildirimler, rozet sayfas\u0131<\/li>\n<\/ul>","raw_excerpt":"Check your WordPress users\u2019 emails against known breaches via verisizintisi.com and act on risks. Language: English | T\u00fcrk\u00e7e \u2192 readme-tr_TR.txt","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/253031","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=253031"}],"author":[{"embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/verisizintisi"}],"wp:attachment":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=253031"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=253031"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=253031"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=253031"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=253031"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=253031"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}