| 开发者 | masseym |
|---|---|
| 更新时间 | 2026年7月5日 14:38 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
composer.lock, package-lock.json, and plugin headers. One click per plugin..pot file in languages/ covers every translatable string. Priority locales for the EU market — German, French, Italian, Spanish, Dutch — are open for community translation via translate.wordpress.org.
wp-content/plugins/mmcra-toolkit/.The EU Cyber Resilience Act (Regulation 2024/2847) applies to any commercial digital product placed on the EU market. For a plugin developer that means you need to identify your manufacturer entity, produce a Software Bill of Materials, publish a coordinated vulnerability disclosure policy, and ship a signed Declaration of Conformity per product. From September 11, 2026, you also have to report actively exploited vulnerabilities to ENISA within 24 hours.
The CRA applies to any product placed on the EU market. If you sell to EU customers — directly or through a marketplace — you're in scope. If you only sell to non-EU customers, the CRA does not apply, but the technical artifacts the toolkit produces are still useful as evidence of secure development practice.
The free version generates SBOMs, Disclosure Policies, and Declarations of Conformity for every plugin you have installed — no plugin limit. Pro adds ongoing weekly OSV.dev vulnerability monitoring (tiered by how many plugins you monitor), incident tracking, AI-assisted triage and drafting, PDF audit reports, and the single-zip Compliance Bundle export for regulator handoff.
Yes. The toolkit outputs CycloneDX 1.6 JSON, which is one of the two SBOM formats explicitly named in the CRA's harmonised standards. The same format works with OWASP Dependency-Track, GitHub Advanced Security, and most enterprise procurement portals.
In a custom table in your WordPress database (wp_mmcra_audit_log). Every artifact written by the toolkit is recorded with timestamp, user, plugin slug, path, and the SHA-256 of the content at write time. This gives you tamper-evident evidence that you produced the file on the date it claims.
No. The free plugin operates entirely on your WordPress install. No telemetry, no phone-home, no third-party API calls. Pro optionally talks to OSV.dev (Google's open-source vulnerability database) for weekly monitoring and to Anthropic's Claude API for AI-assisted triage, both opt-in.
Because the CRA is unfamiliar territory for most plugin developers. The wizard explains what each step is, why the CRA requires it, and what happens if you skip it. You can re-run it any time from CRA Toolkit → Setup Wizard.
composer.lock, package-lock.json, and plugin headers.[mmcra_vdp] shortcode and a rate-limited, honeypot-protected submission form.