iCARRY
Limited data: iCARRY has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Capped at 39: a vulnerability has no patch.
| Ownership | 100 |
|---|---|
| Maintenance | 85 |
| Security | 35 |
| Support | 70 |
| Reputation | 70 |
Quick answers
- Is iCARRY still maintained?
- Yes. Last release 11 Aug 2026, 5 releases in the last 24 months. 11 Aug 2026 · wordpress.org
- Who owns iCARRY, and has it changed hands?
- No change recorded. Main committer icarry since Aug 2024. 4 Nov 2026 · SVN log
- Was iCARRY removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is iCARRY safe?
- No. 1 known vulnerability has no fix in the current version. 10 Aug 2026 · Wordfence Intelligence
- Is the latest iCARRY update safe to install?
- No ownership change before 2.9. No one-star spike after it. 20 Nov 2025 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 10 Aug 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.24 Aug 2026Evidence
- WarningMNT-2Tested up to WordPress 6.8.12, 3 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| plugin-master | 26 Jul 2024 to 26 Jul 2024, 1 commits |
|---|---|
| icarry | 1 Aug 2024 to 11 Aug 2026, 30 commits |
2 committers recorded. No ownership change since 2024.
Maintenance
- Last release
- 3 months ago
- Releases, 24 months
- 5
- Tested up to
- 6.8 vs 7.1
- Requires PHP
- 7.4 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 1 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 3 |
| Q3 2025 | 0 |
| Q4 2025 | 2 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 11 Aug 2026. Tested up to 6.8, 3 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews.
| 5 star | 0 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 0 |
Security record
1 vulnerability in 24 months, 1 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 10 Aug 2026 | iCARRY <= 2.9 - Unauthenticated Information Exposure | 5.3 | <= 2.9 | No fix | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
200+ active installs. History builds with each weekly snapshot.
Momentum history builds with each snapshot.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
No healthier plugin in the same category yet.
Facts
| Version | 2.9 |
|---|---|
| Author | Hassan Fakih |
| Added | 1 Aug 2024 |
| Last updated | 11 Aug 2026 |
| Active installs | 200+ |
| Requires WordPress | 6.0 |
| Tested up to | 6.8.12 |
| Requires PHP | 7.4 |
| Category | not stated |
| Tags | iCARRY, woocommerce, custom shipping |
Questions
Is iCARRY still maintained?
Yes. Last release 11 Aug 2026, 5 releases in the last 24 months.
Who owns iCARRY, and has it changed hands?
No change recorded. Main committer icarry since Aug 2024.
Was iCARRY removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is iCARRY safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest iCARRY update safe to install?
No ownership change before 2.9. No one-star spike after it.