Plugin was previously closed by wp.org for a security issue and has now been reopened. Reopens of security-closed plugins are rare and typically indicate the original author fixed the issue — verify the current committer set matches the pre-closure state, and diff the current trunk against the pre-closure version to confirm no new payload was introduced.
View raw JSON
{
"slug": "sleekplan",
"previously_closed_reason": "security-issue",
"author_slug": "sleekplan",
"current_version": "1.0.0",
"active_installs": 10,
"explanation": "Plugin was previously closed by wp.org for a security issue and has now been reopened. Reopens of security-closed plugins are rare and typically indicate the original author fixed the issue \u2014 verify the current committer set matches the pre-closure state, and diff the current trunk against the pre-closure version to confirm no new payload was introduced."
}
SVN committers (2)
Accounts with actual commit access to sleekplan 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