Backuply – Backup, Restore, Migrate and Clone
If you wait for a fix, how long is the wait?
Across its last 2 feature releases, a follow-up patch arrived in 10–45 days (typically 28 days).
Measured from this plugin's own release history — how quickly a follow-up patch has landed after each feature release. A record of what happened before, not a prediction, and not advice to delay a security fix.
| Version | Released | Threads | Verdict |
|---|---|---|---|
| 1.5.7 | 2026-09-02 | 0 | NO READ |
| 1.5.6 | 2026-08-07 | 0 | NO READ |
| 1.5.5 | 2026-08-06 | 0 | NO READ |
| 1.5.4 | 2026-07-21 | 0 | NO READ |
| 1.5.3 | 2026-05-27 | 0 | NO READ |
| 1.5.2 | 2026-02-26 | 0 | NO READ |
| 1.5.1 | 2025-11-14 | 0 | NO READ |
| 1.5.0 | 2025-09-30 | 0 | NO READ |
| 1.4.9 | 2025-09-17 | 0 | NO READ |
| 1.4.8 | 2025-09-03 | 0 | NO READ |
| 1.4.7 | 2025-07-23 | 0 | NO READ |
| 1.4.6 | 2025-06-17 | 0 | NO READ |
| 1.4.5 | 2025-04-30 | 0 | NO READ |
| 1.4.4 | 2025-04-07 | 0 | NO READ |
| 1.4.3 | 2025-02-10 | 0 | NO READ |
| 1.4.2 | 2025-01-17 | 0 | NO READ |
| 1.4.1 | 2024-11-29 | 0 | NO READ |
| 1.4.0 | 2024-11-19 | 0 | NO READ |
| 1.3.9 | 2024-11-18 | 0 | NO READ |
| 1.3.8 | 2024-11-04 | 0 | NO READ |
| 1.3.7 | 2024-10-22 | 0 | NO READ |
// newest first · thread counts are exact-version matches · verdicts recompute on every sweep