[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ffklnzdIHUaj0-S61Q0HcAePLX5FJNbg8rBHxYay0_0E":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"mtnviewpro","https:\u002F\u002Fprofiles.wordpress.org\u002Fmtnviewpro\u002F",2,0,100,30,94,"2026-08-29T05:42:18.528Z",[13,34],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":7,"num_ratings":7,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"archivioid","ArchivioID","5.1.0","\u003Cp>\u003Cstrong>ArchivioID\u003C\u002Fstrong> is an add-on plugin for \u003Cstrong>ArchivioMD\u003C\u002Fstrong> that adds a full cryptographic identity and signature layer to your WordPress site. It manages GPG public keys, verifies detached OpenPGP signatures on posts, supports multi-signer workflows with configurable thresholds, and exposes public proof pages so anyone can verify authenticity without logging in.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Public Key Management\u003C\u002Fstrong>: Store, manage, and rotate GPG public keys with expiry tracking and administrator alerts\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post Signature Verification\u003C\u002Fstrong>: Upload detached .asc signature files for posts — verified automatically using phpseclib v3\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Browser-Based Signing\u003C\u002Fstrong>: Sign posts directly in the WordPress admin using a browser-held key — no server-side key material required\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Multi-Signature Workflows\u003C\u002Fstrong>: Collect signatures from multiple key holders on a single post; each signer identified by key fingerprint and timestamp\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Configurable Signature Threshold\u003C\u002Fstrong>: Require a minimum number of verified signatures before a post displays the verified badge — configurable globally or per post type\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Algorithm Enforcement Floor\u003C\u002Fstrong>: Block weak signature algorithms (MD5, SHA-1) and enforce minimum RSA\u002FDSA key sizes at upload, REST submission, and re-verification time\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automated Re-Verification\u003C\u002Fstrong>: Daily WP-Cron job re-verifies all signed posts and flags content that has changed since signing\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Key Expiry Notifications\u003C\u002Fstrong>: Email alerts at 30, 14, and 3 days before a key expires, sent to the key owner or site admin\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Key Rotation Workflow\u003C\u002Fstrong>: Admin UI for generating replacement keys, migrating existing signatures, and retiring old keys\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bulk Verification\u003C\u002Fstrong>: Verify all signed posts in a single admin action with per-post status reporting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>REST API\u003C\u002Fstrong>: Full REST endpoint for programmatic signature submission, key retrieval, and verification status\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Key Server\u003C\u002Fstrong>: Publishes active public keys at a stable well-known endpoint for external verifiers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bundle Download\u003C\u002Fstrong>: Downloadable evidence package (hash, signatures, key fingerprints, timestamps) for any post\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Public Proof Pages\u003C\u002Fstrong>: Stable public permalink at \u003Ccode>\u002Farchivio-id\u002Fverify\u002F{post_id}\u003C\u002Fcode> — renders full chain of custody without requiring admin access\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit Logging\u003C\u002Fstrong>: Immutable log of all verification attempts, key changes, and rotation events\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP-CLI Support\u003C\u002Fstrong>: Full CLI interface for batch operations and automated pipelines\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Visual Status Badges\u003C\u002Fstrong>: Front-end badge showing verified \u002F unverified \u002F threshold-unmet status on every post\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 6.0 or higher\u003C\u002Fli>\n\u003Cli>PHP 7.4 or higher (tested up to PHP 8.5)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ArchivioMD plugin version 1.5.0 or higher\u003C\u002Fstrong> (required parent plugin)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Upload your GPG public key via the ArchivioID \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Key Management admin page\u003C\u002Fli>\n\u003Cli>Create or edit a post in WordPress\u003C\u002Fli>\n\u003Cli>Upload a detached .asc signature file for the post, or sign directly in the browser\u003C\u002Fli>\n\u003Cli>ArchivioID verifies the signature immediately and on every subsequent automated re-verify run\u003C\u002Fli>\n\u003Cli>A verification badge appears on the front end; a public proof page is available at a stable permalink\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Technical Details\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Uses \u003Cstrong>phpseclib v3\u003C\u002Fstrong> for all cryptographic operations — no system GPG installation required\u003C\u002Fli>\n\u003Cli>Uses \u003Cstrong>OpenPGP-PHP\u003C\u002Fstrong> for packet parsing and key handling\u003C\u002Fli>\n\u003Cli>All key material and signatures stored in dedicated WordPress database tables\u003C\u002Fli>\n\u003Cli>Algorithm enforcement floor consulted at upload, REST submission, and re-verification time\u003C\u002Fli>\n\u003Cli>Multi-signature threshold evaluated before displaying the verified badge\u003C\u002Fli>\n\u003Cli>Public proof pages require no admin login — safe to share externally\u003C\u002Fli>\n\u003Cli>Fully WordPress coding standards compliant\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>External Services\u003C\u002Fh4>\n\u003Cp>This plugin can make outbound HTTP requests to the following third-party services. \u003Cstrong>All external lookups are opt-in\u003C\u002Fstrong> and can be disabled under ArchivioID \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Key Server Lookup.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>keys.openpgp.org (VKS API)\u003C\u002Fstrong>\u003Cbr \u002F>\nWhen an administrator uses the Key Management page to look up a GPG public key by fingerprint or email address, the plugin sends a GET request to \u003Ccode>https:\u002F\u002Fkeys.openpgp.org\u002Fvks\u002Fv1\u002F\u003C\u002Fcode>. No personal data beyond the fingerprint or email address entered by the administrator is transmitted. This request is made only on explicit administrator action and only when the “Allow key server lookup” setting is enabled.\u003Cbr \u002F>\n* Service: https:\u002F\u002Fkeys.openpgp.org\u003Cbr \u002F>\n* Privacy policy: https:\u002F\u002Fkeys.openpgp.org\u002Fabout\u002Fprivacy\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WKD — Web Key Directory (user’s email domain)\u003C\u002Fstrong>\u003Cbr \u002F>\nWhen an administrator looks up a key by email address, the plugin may also query the Web Key Directory endpoint on the domain portion of that email address (e.g. \u003Ccode>https:\u002F\u002Fexample.com\u002F.well-known\u002Fopenpgpkey\u002F\u003C\u002Fcode>). This follows the OpenPGP Web Key Directory specification (draft-koch-openpgp-webkey-service). The request is made only on explicit administrator action and only when key server lookup is enabled.\u003Cbr \u002F>\n* Specification: https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fdraft-koch-openpgp-webkey-service\u002F\u003Cbr \u002F>\n* The domain contacted is determined entirely by the email address the administrator enters; it is not a fixed third-party service.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Identity Proof URLs (user-supplied)\u003C\u002Fstrong>\u003Cbr \u002F>\nAdministrators may optionally store a public identity proof URL alongside each key (for example, a Keyoxide or Keybase profile page). These URLs are stored in the WordPress database and displayed as links in the frontend badge tooltip. The plugin itself makes no outbound request to these URLs; they are rendered as standard hyperlinks for visitors to follow voluntarily.\u003Cbr \u002F>\n* Keyoxide: https:\u002F\u002Fkeyoxide.org\u003Cbr \u002F>\n* Keybase: https:\u002F\u002Fkeybase.io\u003Cbr \u002F>\n* Any HTTPS URL may be entered; the plugin validates only that the value is a well-formed HTTPS URL.\u003C\u002Fp>\n\u003Ch3>Source Code for Bundled Minified JavaScript\u003C\u002Fh3>\n\u003Cp>This plugin includes \u003Ccode>assets\u002Fjs\u002Fopenpgp.min.js\u003C\u002Fcode>, the minified build of \u003Cstrong>OpenPGP.js\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Project home\u003C\u002Fstrong>: https:\u002F\u002Fopenpgpjs.org\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Source code\u003C\u002Fstrong>: https:\u002F\u002Fgithub.com\u002Fopenpgpjs\u002Fopenpgpjs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>License\u003C\u002Fstrong>: LGPL-3.0-or-later\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Version used\u003C\u002Fstrong>: 5.x (see \u003Ccode>assets\u002Fjs\u002Fopenpgp.min.js\u003C\u002Fcode> file header for exact version)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>To reproduce the minified file from source:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>git clone https:\u002F\u002Fgithub.com\u002Fopenpgpjs\u002Fopenpgpjs.git\u003Cbr \u002F>\ncd openpgpjs\u003Cbr \u002F>\nnpm install\u003Cbr \u002F>\nnpm run build          # produces dist\u002Fopenpgp.min.js\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>Copy \u003Ccode>dist\u002Fopenpgp.min.js\u003C\u002Fcode> to \u003Ccode>assets\u002Fjs\u002Fopenpgp.min.js\u003C\u002Fcode> in this plugin.\u003C\u002Fp>\n\u003Ch3>Security\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>All inputs sanitized and validated; all outputs escaped\u003C\u002Fli>\n\u003Cli>Nonce verification on all forms and AJAX handlers\u003C\u002Fli>\n\u003Cli>Capability checks (\u003Ccode>manage_options\u003C\u002Fcode>) on all admin actions\u003C\u002Fli>\n\u003Cli>REST API write endpoints require authentication\u003C\u002Fli>\n\u003Cli>SQL prepared statements throughout; no raw query interpolation\u003C\u002Fli>\n\u003Cli>Algorithm enforcement floor blocks known-weak cryptographic primitives\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For support, please visit: https:\u002F\u002Fmountainviewprovisions.com\u002Farchivio-id\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under GPLv2 or later.\u003C\u002Fp>\n","OpenPGP signature verification, multi-signer workflows, key lifecycle management, and public proof pages for ArchivioMD.",630,"2026-03-24T00:17:00.000Z","6.9.5","6.0","7.4",[25,26,27,28,29],"authenticity","cryptography","digital-signature","openpgp","security","https:\u002F\u002Fmountainviewprovisions.com\u002FArchivioID","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Farchivioid.zip",null,"2026-07-22T17:31:50.256Z",{"slug":35,"name":36,"version":37,"author":4,"author_profile":5,"description":38,"short_description":39,"active_installs":7,"downloaded":40,"rating":7,"num_ratings":7,"last_updated":41,"tested_up_to":21,"requires_at_least":42,"requires_php":23,"tags":43,"homepage":46,"download_link":47,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"archiviomd","ArchivioMD","1.19.3","\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Built for journalists, compliance teams, legal publishers, and anyone for whom the question “was this changed after it was published?” has a real answer.\u003C\u002Fp>\n\u003Ch4>Content Hashing\u003C\u002Fh4>\n\u003Cp>Every post and page is hashed deterministically on publish and update. A verification badge (✓ Verified \u002F ✗ Unverified \u002F − Not Signed) appears on every post. Verification files are downloadable for offline confirmation. Shortcode: \u003Ccode>[hash_verify]\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Supported algorithms include SHA-256\u002F384\u002F512 family, SHA-3, BLAKE2b\u002F2s, BLAKE3, SHAKE, RIPEMD-160, Whirlpool, and GOST variants.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>HMAC Integrity Mode\u003C\u002Fstrong> adds a shared-secret layer on top of hashing. The key lives in \u003Ccode>wp-config.php\u003C\u002Fcode> — never the database — so an adversary with database access alone cannot silently update a hash.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('ARCHIVIOMD_HMAC_KEY', 'your-secret-key');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Document Signing\u003C\u002Fh4>\n\u003Cp>All signing methods sign the same canonical message and run independently. Any combination can be active simultaneously.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Ed25519\u003C\u002Fstrong> (recommended for most sites) — uses PHP sodium (\u003Ccode>ext-sodium\u003C\u002Fcode>). Private key in \u003Ccode>wp-config.php\u003C\u002Fcode>; public key published at \u003Ccode>\u002F.well-known\u002Fed25519-pubkey.txt\u003C\u002Fcode>. In-browser keypair generator included. Supports DSSE envelope mode (Sigstore spec) with PAE binding to prevent cross-protocol replay.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SLH-DSA \u002F SPHINCS+ (post-quantum)\u003C\u002Fstrong> — 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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>ECDSA P-256\u003C\u002Fstrong> ⚠️ Enterprise\u002Fcompliance 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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>RSA\u003C\u002Fstrong> ⚠️ Legacy compatibility only. Enable when a downstream system cannot accept Ed25519, ECDSA, or SLH-DSA keys.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>CMS \u002F PKCS#7\u003C\u002Fstrong> — Detached DER signatures importable into Adobe Acrobat, Windows Explorer, and enterprise DMS platforms. Reuses your ECDSA or RSA key.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>JSON-LD \u002F W3C Data Integrity\u003C\u002Fstrong> — Produces \u003Ccode>eddsa-rdfc-2022\u003C\u002Fcode> and \u003Ccode>ecdsa-rdfc-2019\u003C\u002Fcode> proof blocks per post and publishes a \u003Ccode>did:web\u003C\u002Fcode> DID document at \u003Ccode>\u002F.well-known\u002Fdid.json\u003C\u002Fcode>. Compatible with ActivityPub, W3C Verifiable Credentials, and decentralised identity wallets.\u003C\u002Fp>\n\u003Cp>All private keys are stored in \u003Ccode>wp-config.php\u003C\u002Fcode> — never in the database. PEM files uploaded via the admin UI are stored outside \u003Ccode>DOCUMENT_ROOT\u003C\u002Fcode>, chmod 0600, with an \u003Ccode>.htaccess\u003C\u002Fcode> Deny guard.\u003C\u002Fp>\n\u003Ch4>DANE \u002F DNS Key Corroboration\u003C\u002Fh4>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Records use the \u003Ccode>amd1\u003C\u002Fcode> tag-value format (modelled on DKIM):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>_archiviomd._domainkey.example.com.  IN TXT \"v=amd1; k=ed25519; p=\u003Cbase64-pubkey>\"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>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 \u003Ccode>\u002F.well-known\u002Farchiviomd-dns.json\u003C\u002Fcode> lists all active records and expected values. A self-describing format specification is served at \u003Ccode>\u002F.well-known\u002Farchiviomd-dns-spec.json\u003C\u002Fcode> regardless of whether DANE is enabled.\u003C\u002Fp>\n\u003Cp>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: \u003Ccode>wp archiviomd dane-check\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>DNSSEC is required for DANE to provide actual security. Most registrars offer it with a single toggle.\u003C\u002Fp>\n\u003Ch4>External Anchoring\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>RFC 3161 Trusted Timestamps\u003C\u002Fstrong> — Sends content hashes to a Time Stamp Authority on every anchor job. The signed \u003Ccode>.tsr\u003C\u002Fcode> 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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Sigstore \u002F Rekor Transparency Log\u003C\u002Fstrong> — Submits a \u003Ccode>hashedrekord\u003C\u002Fcode> 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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Git Repository Anchoring\u003C\u002Fstrong> — Commits integrity records to GitHub or GitLab (public, private, or self-hosted) on every anchor job, creating an independent audit trail in commit history.\u003C\u002Fp>\n\u003Cp>All three anchoring methods can run simultaneously on every job.\u003C\u002Fp>\n\u003Ch4>Document Management\u003C\u002Fh4>\n\u003Cp>Browser-based editing (no FTP) for Markdown meta-documentation (security.txt, privacy policy, terms of service, etc.) and SEO\u002Fcompliance 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.\u003C\u002Fp>\n\u003Ch4>Compliance & Audit Tools\u003C\u002Fh4>\n\u003Cp>Metadata CSV, Compliance JSON, and Backup ZIP exports each generate a companion \u003Ccode>.sig.json\u003C\u002Fcode> 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.\u003C\u002Fp>\n\u003Cp>Manual checksum verification (read-only; does not modify anything). Backup & Restore with mandatory dry-run before any restore operation.\u003C\u002Fp>\n\u003Cp>WP-CLI: \u003Ccode>wp archiviomd process-queue\u003C\u002Fcode>, \u003Ccode>anchor-post \u003Cid>\u003C\u002Fcode>, \u003Ccode>verify \u003Cid>\u003C\u002Fcode>, \u003Ccode>prune-log\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>Canary Tokens (Steganographic Fingerprinting)\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Entirely opt-in. Nothing is injected unless you explicitly enable it.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>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 (\u003Ccode>.sig.json\u003C\u002Fcode>) can be generated after a successful decode for use in legal proceedings.\u003C\u002Fp>\n\u003Cp>Encoding operates across up to 14 channels in three layers:\u003C\u002Fp>\n\u003Cp>\u003Cem>Unicode layer\u003C\u002Fem> (survives copy-paste; stripped by OCR): zero-width characters, thin-space variants, apostrophe variants, soft hyphens.\u003C\u002Fp>\n\u003Cp>\u003Cem>Semantic layer\u003C\u002Fem> (survives OCR and Unicode normalisation; each opt-in): contraction encoding, synonym substitution, punctuation choice, spelling variants, hyphenation choices, number\u002Fdate style, punctuation style II, citation\u002Ftitle style.\u003C\u002Fp>\n\u003Cp>\u003Cem>Structural layer\u003C\u002Fem> (CDN-proof): sentence-count parity, word-count parity.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch4>Ideal For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Journalists and news publishers requiring tamper-evident records\u003C\u002Fli>\n\u003Cli>Legal teams and compliance departments needing auditable document trails\u003C\u002Fli>\n\u003Cli>Organisations subject to HIPAA, ISO 27001, SOC 2, or NIST SP 800-171 requirements\u003C\u002Fli>\n\u003Cli>Whistleblower platforms and activist publishers requiring integrity without platform trust\u003C\u002Fli>\n\u003Cli>Security researchers requiring transparent, verifiable publish records\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Important Notes\u003C\u002Fh4>\n\u003Cp>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 \u003Ccode>uploads\u002Fmeta-docs\u002F\u003C\u002Fcode> and are preserved on uninstall.\u003C\u002Fp>\n\u003Ch3>Getting Started\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Flush Permalinks\u003C\u002Fstrong> — Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Permalinks \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Save Changes. Required for all \u003Ccode>.well-known\u002F\u003C\u002Fcode> endpoints.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Create your first document\u003C\u002Fstrong> — 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.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Enable content hashing\u003C\u002Fstrong> — Go to Cryptographic Verification \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings, choose a hash algorithm (SHA-256 default), save. New and updated posts are hashed automatically from that point.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Configure Ed25519 signing\u003C\u002Fstrong> (optional) — Use the in-browser keypair generator, add both constants to \u003Ccode>wp-config.php\u003C\u002Fcode>, enable signing. Posts, pages, and media are signed automatically on save.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Configure SLH-DSA\u003C\u002Fstrong> (optional) — Navigate to Cryptographic Verification \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> SLH-DSA. Select a parameter set, generate a keypair server-side, add the three constants to \u003Ccode>wp-config.php\u003C\u002Fcode>, enable. Can run alongside Ed25519 (hybrid mode) or standalone.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Enable Rekor \u002F RFC 3161 \u002F Git anchoring\u003C\u002Fstrong> (optional) — Each is configured independently under the ArchivioMD Tools menu. All three can run simultaneously on every anchor job.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Configure DANE\u003C\u002Fstrong> (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.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n","Cryptographic content integrity for WordPress — hashing, signing, RFC 3161 timestamps, Rekor transparency log, and DANE corroboration.",720,"2026-05-09T20:06:00.000Z","5.0",[44,45,26,27,29],"compliance","content-integrity","https:\u002F\u002Fmountainviewprovisions.com\u002FArchivioMD","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Farchiviomd.1.19.3.zip"]