WordPress plugin intelligence profile

CodeMedic SupplyScope

Scans WordPress plugins for vulnerable Composer dependencies and reports CVEs before they become breaches.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.0
Current version1.0.0
WordPress coverageTested up to WordPress 7.0
Minimum stackWP 5.8 · PHP 7.4
Directory statusactive
Last directory update25 Jul 20263mo ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records CodeMedic SupplyScope version 1.0.0 as active, updated 3mo ago and tested up to WordPress 7.0.

Overview

About this plugin

CodeMedic SupplyScope detects vulnerable Composer packages bundled within your WordPress plugins. Every hour, it scans your active plugins against a continuously updated CVE intelligence feed and displays the results in a clear admin dashboard.

Stop guessing which plugins have unpatched vulnerabilities. Get visibility into the hidden dependency chain of every plugin on your site.

How It Works

  • Discovery — Every hour, the plugin scans all active WordPress plugins for bundled Composer dependencies and checks them against our cloud CVE API.
  • Review — Detected vulnerabilities are listed in the admin screen with CVE details, severity, and affected library information.
  • Act — The plugin reports what’s vulnerable so you can take action — whether that means updating the plugin, replacing it, or applying patches manually.

Why Dependency Scanning?

) directly in their vendor directory. Plugin authors may not update these dependencies promptly after a CVE is disclosed. Without a scanner, you have no visibility into these hidden risks.

Patchstack and Wordfence block exploit attempts at the perimeter. This plugin tells you what’s vulnerable so you can take action — whether that means updating the plugin, replacing it, or applying patches manually.

External Services

This plugin queries several third-party vulnerability databases to detect known CVEs in Composer dependencies bundled by your WordPress plugins. No personally identifiable information is transmitted. Each service is described below.

OSV.dev

dev is an open-source vulnerability database maintained by Google. It is used to look up known vulnerabilities in Composer (Packagist) packages.

Data sent: Composer package names and version numbers are sent as JSON in a batch query.

When: On every scheduled scan and when a manual scan is triggered from the admin dashboard.

dev/

com/privacy

National Vulnerability Database (NVD)

S. National Institute of Standards and Technology). It is used to search for CVEs related to WordPress plugins by keyword.

Data sent: The WordPress plugin name is sent as a keyword search query parameter. No personal data is transmitted.

When: On every scheduled scan and when a manual scan is triggered from the admin dashboard.

gov/developers/terms-of-use

gov/privacy-policy

Note: This product uses data from the NVD API but is not endorsed or certified by the NVD.

WPVulnerability.net

net is an open-source WordPress vulnerability database. It provides aggregated vulnerability data for WordPress core, plugins, and themes.

Data sent: The WordPress plugin slug is sent as part of the API URL path. No personal data is transmitted.

When: On every scheduled scan and when a manual scan is triggered from the admin dashboard.

com/license/

com/privacy/

WordPress.org Plugin API

org plugin information API. It is used to retrieve plugin metadata (such as the current stable version and last updated date) to calculate patch velocity metrics.

Data sent: The WordPress plugin slug is sent as a query parameter. No personal data is transmitted.

When: On every scheduled scan and when a manual scan is triggered from the admin dashboard.

org/about/privacy/

org/about/privacy/

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • composer
  • cve
  • dependencies
  • security
  • vulnerabilities
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 7.0

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 5.8 · PHP 7.4
Update activity25 Jul 20263mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.