Plugin released 1.03 (parses as higher than canonical X.0.N series), then later released 1.0.4 which parses LOWER — users who installed the trap version cannot auto-update to the canonical release.
View raw JSON
{
"slug": "cyberimpact-email-marketing-integrations",
"active_traps": [
{
"trap_version": "1.03",
"trap_released": "2025-01-09 15:32:57",
"blocked_by": "1.0.4",
"blocked_on": "2025-02-25 15:03:10"
}
],
"explanation": "Plugin released 1.03 (parses as higher than canonical X.0.N series), then later released 1.0.4 which parses LOWER \u2014 users who installed the trap version cannot auto-update to the canonical release."
}
Plugin released 1.03 (parses as higher than canonical X.0.N series), then later released 1.0.4 which parses LOWER — users who installed the trap version cannot auto-update to the canonical release.
View raw JSON
{
"slug": "cyberimpact-email-marketing-integrations",
"active_traps": [
{
"trap_version": "1.03",
"trap_released": "2025-01-09 15:32:57",
"blocked_by": "1.0.4",
"blocked_on": "2025-02-25 15:03:10"
}
],
"explanation": "Plugin released 1.03 (parses as higher than canonical X.0.N series), then later released 1.0.4 which parses LOWER \u2014 users who installed the trap version cannot auto-update to the canonical release."
}
SVN committers (2)
Accounts with actual commit access to cyberimpact-email-marketing-integrations on plugins.svn.wordpress.org, reconstructed from svn log. This is the list that matters for ownership changes — not the readme contributors.
Names the plugin's readme declares as contributors. A soft signal — anyone can be listed. The SVN access column is the ground-truth cross-reference: does this contributor actually commit code?
WP Beacon