Title: ArchivioMD
Author: mtnviewpro
Published: 21 Febroary 2026
Last modified: 18 Martsa 2026
---
Search plugins
# ArchivioMD
By [mtnviewpro](https://profiles.wordpress.org/mtnviewpro/)
[Download](https://downloads.wordpress.org/plugin/archiviomd.1.19.2.zip)
[Live Preview](https://mg.wordpress.org/plugins/archiviomd/?preview=1)
* [Details](https://mg.wordpress.org/plugins/archiviomd/#description)
* [Reviews](https://mg.wordpress.org/plugins/archiviomd/#reviews)
* [Installation](https://mg.wordpress.org/plugins/archiviomd/#installation)
* [Development](https://mg.wordpress.org/plugins/archiviomd/#developers)
[Support](https://wordpress.org/support/plugin/archiviomd/)
## Description
ArchivioMD gives WordPress sites a cryptographic proof layer. Every post, page,
and document gets a verifiable integrity record — independently checkable without
trusting the platform, the host, or the database.
Built for journalists, compliance teams, legal publishers, and anyone for whom the
question “was this changed after it was published?” has a real answer.
#### Content Hashing
Every post and page is hashed deterministically on publish and update. A verification
badge (✓ Verified / ✗ Unverified / − Not Signed) appears on every post. Verification
files are downloadable for offline confirmation. Shortcode: `[hash_verify]`.
Supported algorithms include SHA-256/384/512 family, SHA-3, BLAKE2b/2s, BLAKE3,
SHAKE, RIPEMD-160, Whirlpool, and GOST variants.
**HMAC Integrity Mode** adds a shared-secret layer on top of hashing. The key lives
in `wp-config.php` — never the database — so an adversary with database access alone
cannot silently update a hash.
```
define('ARCHIVIOMD_HMAC_KEY', 'your-secret-key');
```
#### Document Signing
All signing methods sign the same canonical message and run independently. Any combination
can be active simultaneously.
**Ed25519** (recommended for most sites) — uses PHP sodium (`ext-sodium`). Private
key in `wp-config.php`; public key published at `/.well-known/ed25519-pubkey.txt`.
In-browser keypair generator included. Supports DSSE envelope mode (Sigstore spec)
with PAE binding to prevent cross-protocol replay.
**SLH-DSA / SPHINCS+ (post-quantum)** — pure-PHP implementation of NIST FIPS 205.
No extensions, no Composer dependencies; works on any shared host running PHP 7.4
+. Security rests on SHA-256 alone — not on factoring or discrete logarithms. Four
parameter sets: SLH-DSA-SHA2-128s (default, 7,856-byte signatures), -128f (faster,
17,088 bytes), -192s, -256s. Signing takes 200–600 ms on shared hosting per publish
event — front-end rendering is not affected. Running Ed25519 and SLH-DSA together(
hybrid mode) provides both classical and quantum verifiability from a single DSSE
envelope.
**ECDSA P-256** ⚠️ Enterprise/compliance mode only. Enable when an external framework(
eIDAS, SOC 2, HIPAA, government PKI) explicitly requires X.509 certificate-backed
ECDSA. For all other sites, Ed25519 is recommended. Nonce generation is 100% delegated
to OpenSSL.
**RSA** ⚠️ Legacy compatibility only. Enable when a downstream system cannot accept
Ed25519, ECDSA, or SLH-DSA keys.
**CMS / PKCS#7** — Detached DER signatures importable into Adobe Acrobat, Windows
Explorer, and enterprise DMS platforms. Reuses your ECDSA or RSA key.
**JSON-LD / W3C Data Integrity** — Produces `eddsa-rdfc-2022` and `ecdsa-rdfc-2019`
proof blocks per post and publishes a `did:web` DID document at `/.well-known/did.
json`. Compatible with ActivityPub, W3C Verifiable Credentials, and decentralised
identity wallets.
All private keys are stored in `wp-config.php` — never in the database. PEM files
uploaded via the admin UI are stored outside `DOCUMENT_ROOT`, chmod 0600, with an`.
htaccess` Deny guard.
#### DANE / DNS Key Corroboration
Publishes every active signing key as a DNSSEC-protected DNS TXT record, giving
verifiers a trust path entirely independent of your web server and TLS certificate.
An attacker must compromise both your web host and your DNS zone simultaneously
to forge a key.
Records use the `amd1` tag-value format (modelled on DKIM):
```
_archiviomd._domainkey.example.com. IN TXT "v=amd1; k=ed25519; p="
```
When ECDSA P-256 is configured, an optional TLSA record (RFC 6698, DANE-EE, Selector
=1) binds the leaf certificate to your HTTPS service. A machine-readable discovery
endpoint at `/.well-known/archiviomd-dns.json` lists all active records and expected
values. A self-describing format specification is served at `/.well-known/archiviomd-
dns-spec.json` regardless of whether DANE is enabled.
Weekly passive health checks via wp-cron surface failures as dismissible admin notices.
Key rotation mode suppresses false-positive mismatch warnings during DNS TTL expiry.
Full WP-CLI support: `wp archiviomd dane-check`.
DNSSEC is required for DANE to provide actual security. Most registrars offer it
with a single toggle.
#### External Anchoring
**RFC 3161 Trusted Timestamps** — Sends content hashes to a Time Stamp Authority
on every anchor job. The signed `.tsr` token binds the hash to a specific time and
is independently verifiable offline with OpenSSL. Built-in providers: FreeTSA.org,
DigiCert, GlobalSign, Sectigo. Custom endpoint supported.
**Sigstore / Rekor Transparency Log** — Submits a `hashedrekord` entry to the public
Rekor append-only log (rekor.sigstore.dev) on every anchor job. Entries are immutable
and publicly verifiable without an account or API key. When Ed25519 keys are configured,
entries are signed with the site key; otherwise an ephemeral keypair is generated
automatically.
**Git Repository Anchoring** — Commits integrity records to GitHub or GitLab (public,
private, or self-hosted) on every anchor job, creating an independent audit trail
in commit history.
All three anchoring methods can run simultaneously on every job.
#### Document Management
Browser-based editing (no FTP) for Markdown meta-documentation (security.txt, privacy
policy, terms of service, etc.) and SEO/compliance files: robots.txt, llms.txt,
ads.txt, app-ads.txt, sellers.json, ai.txt. Documents get automatic UUID assignment,
SHA-256 checksum tracking, and an append-only changelog. Standard and comprehensive
XML sitemaps included.
#### Compliance & Audit Tools
Metadata CSV, Compliance JSON, and Backup ZIP exports each generate a companion `.
sig.json` integrity receipt (SHA-256 hash + optional cryptographic signature). The
Compliance JSON export preserves full relationships between posts, hash history,
anchor log entries, and RFC 3161 TSR manifests — suitable for legal evidence packages
and SIEM ingestion.
Manual checksum verification (read-only; does not modify anything). Backup & Restore
with mandatory dry-run before any restore operation.
WP-CLI: `wp archiviomd process-queue`, `anchor-post `, `verify `, `prune-
log`.
#### Canary Tokens (Steganographic Fingerprinting)
**Entirely opt-in. Nothing is injected unless you explicitly enable it.**
Embeds an invisible, HMAC-authenticated fingerprint (post ID + timestamp + 48-bit
MAC) into published content at render time — stored content is never modified. Fingerprints
survive copy-paste and can identify the source of scraped content. A built-in decoder
and DMCA Notice Generator are included. Signed evidence packages (`.sig.json`) can
be generated after a successful decode for use in legal proceedings.
Encoding operates across up to 14 channels in three layers:
_Unicode layer_ (survives copy-paste; stripped by OCR): zero-width characters, thin-
space variants, apostrophe variants, soft hyphens.
_Semantic layer_ (survives OCR and Unicode normalisation; each opt-in): contraction
encoding, synonym substitution, punctuation choice, spelling variants, hyphenation
choices, number/date style, punctuation style II, citation/title style.
_Structural layer_ (CDN-proof): sentence-count parity, word-count parity.
Each bit is encoded three times per active channel with majority-vote redundancy.
A cache compatibility layer ensures fingerprints survive HTML minification by WP
Super Cache, W3 Total Cache, LiteSpeed Cache, WP Rocket, and similar plugins. The
Canary Coverage meta box on the post edit screen shows per-channel slot availability
before you publish.
#### Ideal For
* Journalists and news publishers requiring tamper-evident records
* Legal teams and compliance departments needing auditable document trails
* Organisations subject to HIPAA, ISO 27001, SOC 2, or NIST SP 800-171 requirements
* Whistleblower platforms and activist publishers requiring integrity without platform
trust
* Security researchers requiring transparent, verifiable publish records
#### Important Notes
All metadata is stored in the WordPress database. Regular database backups are required.
All verification, export, and backup operations are admin-triggered and read-only—
the plugin does not prevent or block modifications. Markdown and SEO files are stored
in `uploads/meta-docs/` and are preserved on uninstall.
### Getting Started
1. **Flush Permalinks** — Settings Permalinks Save Changes. Required for all `.well-
known/` endpoints.
2. **Create your first document** — Go to Meta Docs & SEO, pick a predefined file (
e.g. security.txt.md), enter content, save. UUID and first changelog entry are
created automatically.
3. **Enable content hashing** — Go to Cryptographic Verification Settings, choose
a hash algorithm (SHA-256 default), save. New and updated posts are hashed automatically
from that point.
4. **Configure Ed25519 signing** (optional) — Use the in-browser keypair generator,
add both constants to `wp-config.php`, enable signing. Posts, pages, and media
are signed automatically on save.
5. **Configure SLH-DSA** (optional) — Navigate to Cryptographic Verification Settings
SLH-DSA. Select a parameter set, generate a keypair server-side, add the three
constants to `wp-config.php`, enable. Can run alongside Ed25519 (hybrid mode) or
standalone.
6. **Enable Rekor / RFC 3161 / Git anchoring** (optional) — Each is configured independently
under the ArchivioMD Tools menu. All three can run simultaneously on every anchor
job.
7. **Configure DANE** (optional) — Requires at least one signing key. Publish the
DNS TXT records shown in the admin panel, enable DNSSEC on your zone, then enable
DANE Corroboration and run the health check.
## Screenshots
* [[
* Cryptographic Verification — Settings tab showing HMAC Integrity Mode configuration,
including key status indicators and wp-config.php setup instructions.
* [[
* Meta Documentation & SEO Manager — central file manager for meta-documentation
Markdown files, SEO configuration files, and XML sitemaps.
* [[
* Canary Tokens — semantic steganography channel settings, showing the full list
of available fingerprinting channels (contraction encoding, synonym substitution,
spelling variants, and more).
* [[
* Trusted Timestamps (RFC 3161) — anchoring configuration panel with TSA provider
selection, anchor queue status, and activity log with export options.
* [[
* Rekor / Sigstore Transparency Log — server requirements check, Rekor anchoring
settings, and activity log for submissions to the Sigstore public transparency
log.
## Installation
#### Automatic Installation
1. Log in to your WordPress admin panel
2. Navigate to Plugins Add New
3. Search for “ArchivioMD”
4. Click “Install Now” and then “Activate”
5. Navigate to Settings Permalinks and click “Save Changes” (required for `.well-
known/` file serving)
#### Manual Installation
1. Download the plugin ZIP file
2. Upload via Plugins Add New Upload Plugin
3. Activate the plugin
4. Navigate to Settings Permalinks and click “Save Changes”
After activation you will see **Meta Docs & SEO** in the admin sidebar and **ArchivioMD**
under the Tools menu.
## FAQ
### Where are my files stored?
Markdown and SEO files are stored in `uploads/meta-docs/`. Metadata (UUIDs, checksums,
changelogs) is stored in `wp_options` with the prefix `mdsm_doc_meta_`.
### Do I need to back up the database?
Yes. All metadata is stored in the database. The plugin’s Backup & Restore tool
provides portable archives, but standard database backups are still required.
### What happens if I uninstall the plugin?
All files remain in the uploads directory. Database options are only deleted if
you explicitly enable metadata cleanup before uninstalling.
### Does this plugin enforce file integrity?
No. It tracks integrity and provides manual verification tools. Verification is
admin-triggered and read-only — it does not prevent or block modifications.
### Can I verify signatures without WordPress?
Yes. All signing methods are independently verifiable with standard tooling — no
WordPress dependency required.
* **Ed25519:** retrieve the public key from `/.well-known/ed25519-pubkey.txt` and
verify with any sodium-compatible tool.
* **SLH-DSA:** retrieve the public key from `/.well-known/slhdsa-pubkey.txt` and
verify with any FIPS 205-compatible library (e.g. pyspx).
* **ECDSA P-256:** retrieve the certificate from `/.well-known/ecdsa-cert.pem`
and verify with OpenSSL or the Python `cryptography` library.
* **RSA:** retrieve the public key from `/.well-known/rsa-pubkey.pem` and verify
with OpenSSL.
* **CMS/PKCS#7:** decode the base64 DER blob and verify with OpenSSL, Adobe Acrobat,
Java Bouncy Castle, or Windows CertUtil.
* **JSON-LD:** retrieve the DID document from `/.well-known/did.json` and verify
with `@digitalbazaar/jsonld-signatures` (JS) or `pyld` + `cryptography` (Python).
* **RFC 3161:** download the `.tsr` and `.tsq` files from the compliance tools
page and run `openssl ts -verify -in response.tsr -queryfile request.tsq -CAfile
tsa.crt`.
* **Rekor:** use `rekor-cli verify --artifact-hash sha256: --log-index ` or look up the entry at `https://search.sigstore.dev/?logIndex=`.
### When should I use ECDSA P-256 instead of Ed25519?
Only when an external compliance framework explicitly requires X.509 certificate-
backed ECDSA — for example, eIDAS qualified signatures, certain government PKI mandates,
SOC 2 audit requirements specifying certificate-bound signatures, or HIPAA requirements
from a specific assessor. For all other sites, Ed25519 is recommended: simpler to
configure, no certificate expiry to manage, and equally secure.
### When should I use the extended signing formats (RSA, CMS, JSON-LD)?
Use **RSA** only when a downstream system cannot accept Ed25519, ECDSA, or SLH-DSA
keys — for example, older HSMs or legacy enterprise toolchains hardcoded to RSA.
Use **CMS/PKCS#7** when a DMS, Adobe Acrobat workflow, or regulated-industry audit
tool specifically requires `.p7s` format. Use **JSON-LD / W3C Data Integrity** when
building interoperability with ActivityPub implementations, W3C Verifiable Credential
ecosystems, or decentralised identity wallets. For general integrity verification,
Ed25519 covers all common use cases with far less operational overhead.
### Why is SLH-DSA signing slow?
SLH-DSA (SPHINCS+) builds a Merkle tree of hundreds of hash computations per signature.
Because this implementation is pure PHP rather than a native C extension, expect
200–600 ms on shared hosting for the default SHA2-128s parameter set. To reduce
it, switch to SHA2-128f — same NIST Category 1 security, 5–10× faster signing, larger
signatures. This overhead occurs once per publish event and has no effect on front-
end page rendering.
### Should I run Ed25519 and SLH-DSA together?
Yes, if you need verifiability today and quantum resilience for the future. In hybrid
mode the DSSE envelope carries both signatures. Existing verifiers that only understand
Ed25519 continue to work unchanged.
### Does Rekor require an API key?
No. The public good instance (rekor.sigstore.dev) is a free, unauthenticated API
operated by the Linux Foundation’s Sigstore project.
### Does DANE Corroboration require DNSSEC?
Yes. Without DNSSEC, DNS responses are unauthenticated and the TXT records provide
no additional trust over the web server alone. Most registrars now offer DNSSEC
with a single toggle.
### Is this plugin GDPR compliant?
The plugin does not collect, store, or process personal data from visitors. It stores
administrative metadata associated with WordPress user accounts. Compliance with
GDPR depends on how you use the plugin — consult your legal team.
### Can non-admin users access these features?
No. All features require the `manage_options` capability (administrator role).
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“ArchivioMD” is open source software. The following people have contributed to this
plugin.
Contributors
* [ mtnviewpro ](https://profiles.wordpress.org/mtnviewpro/)
[Translate “ArchivioMD” into your language.](https://translate.wordpress.org/projects/wp-plugins/archiviomd)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/archiviomd/), check
out the [SVN repository](https://plugins.svn.wordpress.org/archiviomd/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/archiviomd/) by
[RSS](https://plugins.trac.wordpress.org/log/archiviomd/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.19.2
* Added five admin screenshots to the WordPress plugin directory listing, covering
Cryptographic Verification settings, Meta Documentation & SEO Manager, Canary
Tokens channel settings, Trusted Timestamps (RFC 3161), and Rekor / Sigstore
Transparency Log. No functional changes.
#### 1.19.1
* Fixed verification badge text (“Verified”) appearing as plain text in search
engine title tags when Yoast SEO (and other SEO plugins) are active. SEO plugins
call `get_the_title()` while building the `` tag before `wp_head` completes;
the badge HTML was being appended, stripped of its tags, and indexed as part
of the post title. Badge now only injects after `wp_head` has fired, ensuring
it renders in the page body only and is never seen by search engines.
#### 1.19.0
* Fixed custom markdown files returning 404. WordPress rewrite rules now register
routes for both the root path and the `/.well-known/meta-docs/` path, which is
where the file manager stores custom files by default. Previously only the root-
level route was registered, so any request to the `.well-known` path fell through
to a 404.
* Fixed unreliable rewrite rule flushing after creating or deleting a custom markdown
file via the admin UI. `flush_rewrite_rules()` called inside an AJAX handler
does not always persist reliably; the fix schedules a guaranteed follow-up flush
on the next real page load via a transient flag.
* Added ArchivioID PGP Validator support to the browser extension. The extension
now calls the ArchivioID REST API (`/wp-json/archivio-id/v1/posts/{id}/signatures`),
retrieves all PGP signature records, fetches public keys from `keys.openpgp.org`
by fingerprint, and performs client-side cryptographic verification using OpenPGP.
js (Ed25519, RSA, ECDSA supported). Results are surfaced as Step 8 in the full
verification report.
* Hardened REST API verification endpoint: added per-IP rate limiting (60 req/min),
restricted URL resolution to the site’s own domain to prevent cross-origin post
enumeration, replaced table-name SQL interpolation with a whitelisted identifier
check, changed `Cache-Control` on `/verify` from `public` to `private` to prevent
shared-proxy caching of verification status, and reduced `/status` cache TTL
to prevent stale feature-flag disclosure.
#### 1.17.4
* Fixed version mismatch: plugin header `Version` and `MDSM_VERSION` constant were
stuck at 1.16.0 across the 1.17.x release series. Both now correctly read 1.17.4
and match the readme `Stable tag`.
#### 1.17.3
* Added `/.well-known/archiviomd-dns-spec.json` — a machine-readable, self-contained
specification for the `amd1` TXT record format, the TLSA profile, the canonical
message format, and the end-to-end verification flow.
* `archiviomd-dns.json` now includes a `spec_url` field pointing to the spec endpoint.
#### 1.17.2
* Added TLSA cert-expiry staleness warning (≤ 30 days warns, expired errors).
* Added `ARCHIVIOMD_DANE_TTL` constant; TTL now configurable and used consistently
across rotation threshold, admin UI, and `Cache-Control` headers.
* Added ETag / `If-None-Match` / 304 conditional response support to the discovery
endpoint.
* Fixed discovery endpoint returning HTTP 404 when DANE disabled — now returns
HTTP 200 with `{"enabled":false}` so verifiers can distinguish module-off from
a wrong URL.
* Fixed DoH network timeout surfacing as a false “DNSSEC not validated” admin notice.
#### 1.17.1
* Added TLSA / DANE-EE support (RFC 6698) for the ECDSA P-256 certificate. Selector
=1 (SubjectPublicKeyInfo) so the record survives certificate renewal without
a key change.
* Added copy-to-clipboard buttons for all DNS TXT record values in the admin UI.
* Fixed `Cache-Control` bug in the discovery endpoint that overwrote the intended`
public, max-age=3600` header.
* Added `--enable` and `--disable` flags to `wp archiviomd dane-check`.
#### 1.17.0
* Added DANE / DNS Key Corroboration. Publishes Ed25519, SLH-DSA, ECDSA P-256,
and RSA public keys as DNSSEC-protected DNS TXT records in the custom `amd1`
format. DoH-based health checks, weekly passive cron, key rotation workflow,
machine-readable discovery endpoint at `/.well-known/archiviomd-dns.json`, JSON-
LD integration, and WP-CLI `wp archiviomd dane-check`.
#### 1.16.0
* Added RSA Compatibility Signing (Extended Format). RSA-PSS/SHA-256 (recommended)
and PKCS#1 v1.5/SHA-256. Minimum key size 2048 bits enforced. Public key published
at `/.well-known/rsa-pubkey.pem`.
* Added CMS / PKCS#7 Detached Signatures (Extended Format). DER blob importable
directly into Adobe Acrobat and enterprise DMS platforms as `.p7s`. Reuses existing
ECDSA or RSA key.
* Added JSON-LD / W3C Data Integrity Proofs (Extended Format). Cryptosuites `eddsa-
rdfc-2022` and `ecdsa-rdfc-2019`. DID document at `/.well-known/did.json`.
* All three new methods are opt-in, disabled by default, and sign the same canonical
message as all other methods.
#### 1.15.0
* Added ECDSA P-256 document signing (Enterprise / Compliance Mode). Nonce generation
delegated entirely to OpenSSL. Certificate validated on every signing operation.
Private keys stored outside `DOCUMENT_ROOT`, chmod 0600. Leaf certificate published
at `/.well-known/ecdsa-cert.pem`.
#### 1.14.0
* Added SLH-DSA (SPHINCS+) post-quantum document signing — NIST FIPS 205, pure
PHP, no extensions or Composer dependencies. Four parameter sets: SHA2-128s (
default), SHA2-128f, SHA2-192s, SHA2-256s. Hybrid mode with Ed25519 via shared
DSSE envelope.
#### 1.13.1
* Fixed SSRF in the URL decoder (`ajax_decode_url()`): hostname now resolved via`
dns_get_record()` with full private/loopback range rejection and cURL IP pinning
to prevent TOCTOU.
* Fixed rate limiter bypass via `X-Forwarded-For`: now uses rightmost IP with private-
range validation, falls back to `REMOTE_ADDR`.
* Fixed evidence receipts signed over arbitrary POST data: handler now fetches
the authoritative server-written log row by ID.
* Fixed key rotation warning that could not be dismissed (wrong option key names
in delete calls).
* Fixed three canary option keys missing from the site-specific obfuscation map(
fell through to a site-agnostic fallback, defeating the scheme).
* Fixed ReDoS in `extract_main_content()`: input capped at 2 MB; `DOMDocument`
used as primary extractor; regex fallback uses bounded quantifiers.
* Removed `sslverify => false` from all outbound fetches.
* Added persistent admin notice when `ARCHIVIOMD_HMAC_KEY` is not defined in `wp-
config.php`.
#### 1.13.0
* Added Ch.13 (Sentence-count parity) and Ch.14 (Word-count parity) structural
fingerprinting channels — CDN-proof, survive Unicode normalisation.
* Added `Cache-Control: no-transform` header on all fingerprinted responses.
* Renamed REST endpoints from `archiviomd/v1/canary-check` to `content/v1/verify`
to reduce plugin fingerprinting via API enumeration.
* Added `.htaccess` to plugin root blocking direct HTTP access to `.php`, `.txt`,`.
json`, and other source files.
* Added key-derived pair selection for Ch.5/6/8/9: active dictionary subset is
site-specific, making adversarial reversal equivalent to key brute-force.
* Added `wp_options` key obfuscation for all Canary Token settings.
#### 1.12.0
* Added Cache Compatibility Layer. Detects and repairs Unicode fingerprint stripping
by WP Super Cache, W3 Total Cache, LiteSpeed Cache, WP Rocket, and other HTML-
minifying caching plugins — no caching plugin configuration required.
#### 1.11.0
* Added Canary Token channels Ch.8–Ch.12: Spelling Variants (60+ British/American
pairs), Hyphenation Choices (30+ compound pairs), Number/Date Style, Punctuation
Style II, Citation/Title Style.
#### 1.10.0
* Added REST API fingerprinting (closes WP REST API scraping path).
* Added rate limiting on public verification endpoint (60 req/min; HTTP 429).
* Added Key Health Monitor with persistent admin notice on HMAC key change.
* Added Discovery Log (`wp_archivio_canary_log`) with CSV export.
* Added Signed Evidence Package — `.sig.json` receipt with SHA-256 + optional Ed25519
signature for each decode event.
* Added Re-fingerprint All Posts bulk action (single atomic SQL upsert).
* Added Canary Coverage meta box on the post edit screen.
* Added Ch.7 (Punctuation Choice: Oxford comma, em-dash/parentheses).
* Added URL Decoder and DMCA Notice Generator tabs.
For versions prior to 1.8.0, see the full changelog on the plugin’s development
repository.
## Meta
* Version **1.19.2**
* Last updated **4 herinandro ago**
* Active installations **Fewer than 10**
* WordPress version ** 5.0 or higher **
* Tested up to **6.9.4**
* PHP version ** 7.4 or higher **
* Language
* [English (US)](https://wordpress.org/plugins/archiviomd/)
* Tags
* [compliance](https://mg.wordpress.org/plugins/tags/compliance/)[cryptography](https://mg.wordpress.org/plugins/tags/cryptography/)
[digital signature](https://mg.wordpress.org/plugins/tags/digital-signature/)
[security](https://mg.wordpress.org/plugins/tags/security/)
* [Advanced View](https://mg.wordpress.org/plugins/archiviomd/advanced/)
## Ratings
Mbola tsy misy domberina voaray hatreto.
[Your review](https://wordpress.org/support/plugin/archiviomd/reviews/#new-post)
[Hijery ny domberina rehetra](https://wordpress.org/support/plugin/archiviomd/reviews/)
## Contributors
* [ mtnviewpro ](https://profiles.wordpress.org/mtnviewpro/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/archiviomd/)