Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

Viktor’s Login Probe Protection

by Viktor Szépe · Fewer than 10 active installs · Checked 4 Nov 2026
Limited data

Limited data: Viktor’s Login Probe Protection has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

95/ 100Limited data
Canary Score

Based on 3 of 5 areas

Capped at 95: not enough support or review data for a full score.

Sub-scores for Viktor’s Login Probe Protection
Ownership100
Maintenance100
Security100
SupportNo data
ReputationNo data

How the score works

Active signals

Open issues right now, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Quick answers

Is Viktor’s Login Probe Protection still maintained?
Yes. Last release 21 Aug 2026, 3 releases in the last 24 months. 21 Aug 2026 · wordpress.org
Who owns Viktor’s Login Probe Protection, and has it changed hands?
No change recorded. Main committer szepe.viktor since Aug 2026. 4 Nov 2026 · SVN log
Was Viktor’s Login Probe Protection removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
Is Viktor’s Login Probe Protection safe?
No known vulnerabilities on record. 4 Nov 2026 · Wordfence Intelligence
Is the latest Viktor’s Login Probe Protection update safe to install?
No ownership change before 1.1.0. No one-star spike after it. 21 Aug 2026 · Release history

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
plugin-master7 Aug 2026 to 7 Aug 2026, 1 commits
szepe.viktor7 Aug 2026 to 21 Aug 2026, 4 commits

2 committers recorded. No ownership changes recorded since 2026.

Maintenance

Last release
3 months ago
Releases, 24 months
3
Tested up to
7.1 current
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for Viktor’s Login Probe Protection
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20263
Q4 20260

Last release 21 Aug 2026. Tested with WordPress 7.1 (current).

Support

Resolved, last 2 months
n/a
Threads, last 2 months
0

Trend appears after 8 weekly snapshots.

Security record

No published vulnerabilities on record for this plugin.

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Reputation

Last 90 days: no reviews.

Rating distribution
5 star0
4 star0
3 star0
2 star0
1 star0

Momentum

Active installs
Fewer than 10

Trend appears after 8 weekly snapshots.

Facts

Version
1.1.0
Author
Viktor Szépe
Added
7 Aug 2026
Last updated
21 Aug 2026
Active installs
Fewer than 10
Requires WordPress
6.0
Tested up to
7.1.4
Requires PHP
7.4
Category
not stated
Tags
login, security, woocommerce

Other plugins by this author: Password bcrypt, Multipart robots.txt editor, Custom settings for Sucuri Scanner, Plugin Installer Speedup, Tiny CDN, Manual Cron, Resource Versioning, SMTP URI and logging, Solarized Admin Color Scheme, SVN Updater, Plugin changelog checker, What's running

Questions about Viktor’s Login Probe Protection

Is Viktor’s Login Probe Protection still maintained?

Yes. Last release 21 Aug 2026, 3 releases in the last 24 months.

Who owns Viktor’s Login Probe Protection, and has it changed hands?

No change recorded. Main committer szepe.viktor since Aug 2026.

Was Viktor’s Login Probe Protection removed from wordpress.org?

No. Listed on wordpress.org as of 4 Nov 2026.

Is Viktor’s Login Probe Protection safe?

No known vulnerabilities on record.

Is the latest Viktor’s Login Probe Protection update safe to install?

No ownership change before 1.1.0. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 4 Nov 2026.Report a data issue