LeadBooster Chatbot by Pipedrive
Healthy: maintained, last release 10 Jun 2026, no unpatched vulnerabilities.
| Ownership | 100 |
|---|---|
| Maintenance | 85 |
| Security | 100 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is LeadBooster Chatbot by Pipedrive still maintained?
- Yes. Last release 10 Jun 2026, 0 releases in the last 24 months. 10 Jun 2026 · wordpress.org
- Who owns LeadBooster Chatbot by Pipedrive, and has it changed hands?
- No change recorded. Main committer vodacek since Aug 2019. 3 Nov 2026 · SVN log
- Was LeadBooster Chatbot by Pipedrive removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is LeadBooster Chatbot by Pipedrive safe?
- No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
- Is the latest LeadBooster Chatbot by Pipedrive update safe to install?
- No ownership change before 1.1.1. No one-star spike after it. 28 Nov 2022 · Release history
Active signals
Facts we detected, with links to the source.
No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| plugin-master | 7 Jun 2019 to 7 Jun 2019, 1 commits |
|---|---|
| tomasrehor | 8 Jun 2019 to 8 Jun 2019, 2 commits |
| redoper | 10 Jun 2019 to 15 Nov 2021, 13 commits |
| vodacek | 5 Aug 2019 to 10 Jun 2026, 19 commits |
| pditops | 5 Jan 2022 to 5 Jan 2022, 1 commits |
5 committers recorded. No ownership change since 2019.
Maintenance
- Last release
- 5 months ago
- Releases, 24 months
- 0
- Tested up to
- 7.0 vs 7.1
- Requires PHP
- 5.6 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 0 |
| Q4 2025 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 10 Jun 2026. Tested up to 7.0, 1 major version behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 3.7.
| 5 star | 2 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 1 |
Security record
No published vulnerabilities on record for this plugin.
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
2,000+ active installs. History builds with each weekly snapshot.
| 4 May 2026 | 20 |
|---|---|
| 11 May 2026 | 42 |
| 18 May 2026 | 50 |
| 25 May 2026 | 57 |
| 1 Jun 2026 | 52 |
| 8 Jun 2026 | 97 |
| 15 Jun 2026 | 48 |
| 22 Jun 2026 | 42 |
| 29 Jun 2026 | 53 |
| 6 Jul 2026 | 54 |
| 13 Jul 2026 | 55 |
| 20 Jul 2026 | 69 |
| 27 Jul 2026 | 70 |
| 3 Aug 2026 | 137 |
| 10 Aug 2026 | 59 |
| 17 Aug 2026 | 179 |
| 24 Aug 2026 | 164 |
| 31 Aug 2026 | 71 |
| 7 Sep 2026 | 86 |
| 14 Sep 2026 | 81 |
| 21 Sep 2026 | 93 |
| 28 Sep 2026 | 151 |
| 5 Oct 2026 | 137 |
| 12 Oct 2026 | 101 |
| 19 Oct 2026 | 171 |
| 26 Oct 2026 | 150 |
| 2 Nov 2026 | 19 |
Weekly downloads over the last 4 weeks are 29% above the 27-week average.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
Facts
| Version | 1.1.1 |
|---|---|
| Author | Pipedrive |
| Added | 8 Jun 2019 |
| Last updated | 10 Jun 2026 |
| Active installs | 2,000+ |
| Requires WordPress | 4.5 |
| Tested up to | 7.0.8 |
| Requires PHP | 5.6 |
| Category | Customer Management > CRM & Customer Database |
| Tags | chat, customer, livechat, live chat, Pipedrive |
Questions
Is LeadBooster Chatbot by Pipedrive still maintained?
Yes. Last release 10 Jun 2026, 0 releases in the last 24 months.
Who owns LeadBooster Chatbot by Pipedrive, and has it changed hands?
No change recorded. Main committer vodacek since Aug 2019.
Was LeadBooster Chatbot by Pipedrive removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is LeadBooster Chatbot by Pipedrive safe?
No known vulnerabilities on record.
Is the latest LeadBooster Chatbot by Pipedrive update safe to install?
No ownership change before 1.1.1. No one-star spike after it.