WordPress plugin intelligence profile

Dragon Compliance – CRA & NIS2 Compliance, SBOM Export & Vulnerability Scanner

CRA and NIS2 compliance for WordPress: software inventory, SBOM export, vulnerability scanning, readiness checklist and a timestamped evidence log.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.1.0
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.2 · PHP 8.0
Directory statusactive
Last directory update10 Oct 202622d 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 Dragon Compliance – CRA & NIS2 Compliance, SBOM Export & Vulnerability Scanner version 1.1.0 as active, updated 22d ago and tested up to WordPress 7.1.

Overview

About this plugin

The EU Cyber Resilience Act (CRA) and the NIS2 directive expect the businesses

they cover to know what software they run, monitor it for known

vulnerabilities, patch without delay – and to be able to prove all of that.

Dragon Compliance turns your WordPress site into something you can hand to an

auditor:

  • Software inventory – WordPress core, every plugin and theme with version,

author and license, plus the PHP/database/server environment.

  • SBOM export – download a standards-compliant CycloneDX 1.6 JSON Software

Bill of Materials, the artifact auditors and enterprise customers ask for.

  • Vulnerability monitoring that works out of the box – a daily scan checks

WordPress core and every installed plugin and theme against the free

WPVulnerability database, with no account or API key, and lists affected

components by severity with CVE links. A component that could not be checked

is shown as “not checked”, never as clear. If you prefer, switch to the

Wordfence Intelligence feed with your own free token.

  • Vulnerability alerts – new critical findings, and new findings whose

severity has not been published yet, are emailed to the site admin or to a

list of addresses you choose.

  • CRA readiness checklist – automatic checks (HTTPS, auto-updates coverage,

debug mode, file editing, 2FA, default admin account, open criticals) plus

manual attestations for process facts like your update policy and backups,

with a completion score.

  • Evidence log – every scan, detection, resolution and attestation change

is recorded with a timestamp, building the audit trail regulators expect.

Matching, findings and the evidence log all stay in your WordPress database.

To check for known vulnerabilities, the plugin asks a public vulnerability

database about your installed components (see External services below): it

sends component names and the WordPress version, never your site address,

users or content.

Everything above is free, fully functional and unlimited.

External services

This plugin connects to one vulnerability database at a time, chosen under

Tools → Compliance → Settings. Both are used only for vulnerability

monitoring: once a day, after you add, update or remove a plugin or theme,

when you press “Scan now”, and once more shortly after a scan that ran out of

time before every component was looked up.

WPVulnerability (default)

com) is a free, public database

of known WordPress vulnerabilities. By default the plugin asks

net about each installed component: the slug (folder

name) of every plugin and theme, and the WordPress core version number. Plugin

and theme versions are not sent; the plugin compares versions on your server.

Your site address, users and content are not sent; like any web request, the

service sees your server’s IP address. Answers are cached on your site for

12 hours. No account or API key is needed.

0.

com/privacy/

com/license/

Wordfence Intelligence (only when you choose it)

If you select Wordfence Intelligence and enter your own API token, the plugin

instead downloads the full Wordfence Intelligence vulnerability list from

) and matches it on your server.

Only your API token is sent with that request – no data about your site, its

inventory or its users. Without a token nothing is sent to Wordfence. You need

com account to generate a token.

com/terms-of-use/

com/privacy-policy/

Credits

dev), ISC License. com, MIT License). All other copyright (c) for Lucide are held by Lucide Contributors 2022.

The plugin itself does not include these icons.

WordPress.org metadata

Plugin tags

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

  • vulnerability scanner
  • compliance
  • nis2
  • sbom
  • security
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.2 · PHP 8.0
Update activity10 Oct 202622d 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

Version1.0.131.1.0
WordPress compatibility7.1.27.1.3
Version1.0.121.0.13
Version1.0.111.0.12
Version1.0.101.0.11
Version1.0.91.0.10
WordPress compatibility7.17.1.2
Version1.0.81.0.9
Version1.0.71.0.8
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.