by mtnviewpro 0 (0 reviews)

ArchivioMD

Name: ArchivioMD
Author: mtnviewpro

Cryptographic content integrity for WordPress — hashing, signing, RFC 3161 timestamps, Rekor transparency log, and DANE corroboration.

ArchivioMD ranks #56,222 among WordPress.org plugins with 0+ active installations, is #3,076 of 4,265 in the SEO & Marketing category, and was last updated May 10, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 6.9.11 (Current: 7.1.4)

v1.19.3 Current Version v1.19.3

Updated 5 months ago Last Update on 10 May, 2026

Refreshed 1 week ago Last Refreshed on

#3,076 of 4,265 in SEO & Marketing

View on WordPress.org

Rank

#56,222

— No change

Active Installs

-100%

KW Avg Position

112.3

1 worse

Downloads

924

+10 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

28,654

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 7 more installs to reach 10+

Rank Changes

Current #56,222

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.19.3
Last Updated: May 10, 2026
Requires WP: 5.0+
Tested Up To: 6.9.11
PHP Version: 7.4 or higher
Author: mtnviewpro

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

compliance content-integrity cryptography digital signature security

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

Yoast SEO – Advanced SEO with real-time guidance and built-in AI

10M+ installs

$Rank Math SEO – AI SEO Tools to Dominate SEO Rankings$

Rank Math SEO – AI SEO Tools to Dominate SEO Rankings

All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)

2M+ installs

#22

MC4WP: Mailchimp for WordPress

1M+ installs

#35

Hostinger Reach – AI-Powered Email Marketing for WordPress

1M+ installs

#41

XML Sitemap Generator for Google

View all Seo-and-marketing plugins

Frequently Asked Questions

Common questions about ArchivioMD

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_.

Yes. All metadata is stored in the database. The plugin's Backup & Restore tool provides portable archives, but standard database backups are still required.

All files remain in the uploads directory. Database options are only deleted if you explicitly enable metadata cleanup before uninstalling.

No. It tracks integrity and provides manual verification tools. Verification is admin-triggered and read-only — it does not prevent or block modifications.

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:<HASH> --log-index <INDEX> or look up the entry at https://search.sigstore.dev/?logIndex=<INDEX>.

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.

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.

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.

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.

No. The public good instance (rekor.sigstore.dev) is a free, unauthenticated API operated by the Linux Foundation's Sigstore project.