Skip to content
Sign In Create account

DigiAudit

Scores a WordPress site out of 100, explains every problem it finds — what was seen, why it matters to the business, how it gets fixed — and lets the owner ask us for a quote on the ones they want fixed.

v1.0.3 90.9 KB GPL-2.0-or-later WordPress.org

DigiAudit

What it does

It runs from inside the site, so it sees what an outside scanner cannot: plugin and theme versions, wp-config.php, scheduled tasks, the database and the error log, as well as the headers, certificate and pages a visitor gets. Every check only reads; nothing on the site is changed. The admin screens, e-mails and report are in French.

  • A score and a grade

    Out of 100 with a grade from A to E, a score per category, and the change since the previous scan.

  • 56 checks in four groups

    Security (23), performance (11), SEO (14) and maintenance (8) — from abandoned plugins and exposed backups to the sitemap and overdue cron jobs.

  • Written for the owner

    Each problem says what was found, why it matters in business terms, the recommended fix and whether that is a quick, standard or advanced job.

  • A quote in one click

    Tick the problems, fill in a short form and send it. The owner gets a reference number and an acknowledgement by e-mail.

  • A weekly scan

    In the background through WP-Cron, with an e-mail when a new critical problem appears or the score drops by 10 points or more.

  • A printable report

    The full result on one page, to save as PDF from the browser, plus a dashboard widget and a badge in the admin menu.

The full manual: every screen, setting and check, step by step

What it needs

WordPress
5.8 or newer
PHP
7.4 or newer
PHP extensions
No extension beyond a standard PHP build.

Install it

From the WordPress.org directory

The shortest way: WP-CLI downloads the current release from WordPress.org over HTTPS and activates it. To check the file yourself first, use the command after it.

bash
wp plugin install digipacket-site-audit --activate --path=/path/to/wordpress

Or, in WordPress: Plugins → Add New Plugin, search for the name above, then Install Now and Activate.

The whole install, in one command

Downloads, checks the file against the SHA-256 below, unpacks it into your plugins directory and cleans up after itself. Any step that fails stops the rest.

bash
cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://downloads.wordpress.org/plugin/digipacket-site-audit.1.0.3.zip \
  && echo "3a238e6b2fea90411b276c2c0d4e837c27f5063a44c068d053c5127905a7e9c5  digipacket-site-audit.1.0.3.zip" | sha256sum -c - \
  && unzip -q digipacket-site-audit.1.0.3.zip \
  && rm digipacket-site-audit.1.0.3.zip

Activate it

With WP-CLI. Without WP-CLI, the plugin is now listed under Plugins → Installed Plugins and the button there does the same thing.

bash
wp plugin activate digipacket-site-audit --path=/path/to/wordpress

Why the commands look like this

  • Why -f is not optional

    Without it, curl writes the server's error page into your file and exits 0. You unzip an HTML document into wp-content/plugins and WordPress shows a broken plugin. With -f, curl writes nothing and exits 22.

  • Why the checksum is printed here

    A hash served next to the file only proves the download was not corrupted in transit. This page is a second channel: if the number here and the number on the file agree, both would have had to be changed.

  • Why the steps are chained with &&

    A semicolon runs the next command whether or not the last one worked. With &&, a failed download or a failed checksum stops the chain before anything is written into your plugins directory.

Verify the download

Version
1.0.3
File
digipacket-site-audit.1.0.3.zip
Size
90.9 KB 93,052 bytes
SHA-256
3a238e6b2fea90411b276c2c0d4e837c27f5063a44c068d053c5127905a7e9c5
Published
2 November 2026

Check what you downloaded

Prints OK, or names the file and exits non-zero. Run it before you unpack anything.

bash
# GNU coreutils, on a Linux server
echo "3a238e6b2fea90411b276c2c0d4e837c27f5063a44c068d053c5127905a7e9c5  digipacket-site-audit.1.0.3.zip" | sha256sum -c -

# macOS, and anywhere sha256sum is missing
echo "3a238e6b2fea90411b276c2c0d4e837c27f5063a44c068d053c5127905a7e9c5  digipacket-site-audit.1.0.3.zip" | shasum -a 256 -c

Check what is installed

Compares every file in the plugin folder against the checksums WordPress.org publishes for that version, and names any file that differs or should not be there. It works on a copy installed any way at all.

bash
wp plugin verify-checksums digipacket-site-audit --path=/path/to/wordpress

Always the newest release

The pinned URL above is the one to use in documentation and in a change you want to be able to repeat. A provisioning script usually wants whatever is current — and WordPress.org serves exactly that at an address with no version in it.

That file has no fixed checksum

The unversioned file is always the current stable release, so its hash changes with every release. Comparing it against the hash on this page works today and fails on the next release — which teaches a script to skip the check.

Download the unversioned file, and once it is installed let WP-CLI check every file against the checksums WordPress.org publishes for that exact version:

Whatever the current release is

The file WordPress.org serves under the plugin's name alone, then the per-file check once it is installed.

bash
cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://downloads.wordpress.org/plugin/digipacket-site-audit.zip \
  && unzip -q digipacket-site-audit.zip \
  && rm digipacket-site-audit.zip \
  && wp plugin verify-checksums digipacket-site-audit --path=/path/to/wordpress

Update it

Removing the folder first is safe for your data: scans, history, settings and the quote log are in the WordPress database. It does replace config.php — if you changed it, apply the change again, or move it to the digipacket_audit_agency_config filter in a must-use plugin, where an update cannot reach it.

Update an existing install

Same chain, with the old directory removed before the new one is written. Unzipping over the top would leave files from the previous version behind.

bash
cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://downloads.wordpress.org/plugin/digipacket-site-audit.1.0.3.zip \
  && echo "3a238e6b2fea90411b276c2c0d4e837c27f5063a44c068d053c5127905a7e9c5  digipacket-site-audit.1.0.3.zip" | sha256sum -c - \
  && rm -rf digipacket-site-audit \
  && unzip -q digipacket-site-audit.1.0.3.zip \
  && rm digipacket-site-audit.1.0.3.zip \
  && wp plugin activate digipacket-site-audit --path=/path/to/wordpress

Remove it

Remove it

Deactivates first, so WordPress runs the plugin's own deactivation code rather than having the directory disappear underneath it.

bash
wp plugin deactivate digipacket-site-audit --path=/path/to/wordpress \
  && wp plugin delete digipacket-site-audit --path=/path/to/wordpress

What it sends

A scan makes one kind of outside request, and nothing else leaves the site until the owner acts. This is the list a privacy policy needs.

  • During a scan: the slug of each installed plugin, up to 50, to api.wordpress.org — to learn whether it was closed or has not been updated for two years. Answers are kept for three days. Every other request in a scan goes to the site itself.
  • When the owner sends a quote request, and only after they tick the consent box: their name, company, e-mail, phone, preferred contact method, urgency and message, the problems they selected and the others found, the score, and the site's environment — address, WordPress and PHP versions, theme and active plugins. It goes by e-mail, through the site's own wp_mail(), to [email protected].
  • When the owner has turned on proactive support — it is off by default — and a weekly scan finds a new critical problem: the new problems, the score, the WordPress and PHP versions and the contact details from the plugin's settings, by e-mail to the same address.
  • Nothing goes to a webhook unless one is written into config.php. The published release has none.

What it does not do

Written down for the same reason as everything else on this page: finding out after you have installed it is worse.

  • It finds problems; it does not fix them. Every check only reads, and the fixes are the work a quote request asks us for.
  • The interface, the e-mails and the report are in French. The strings are translation-ready under the digiaudit text domain, but no translation ships.
  • A quote request is an e-mail sent by the site's own server. Where that server cannot send mail, the request is logged as failed in the plugin's history and does not reach us — the "Fiabilité des e-mails" check is there to warn about exactly that.
  • The weekly scan runs on WP-Cron, which runs when the site has visitors. On a site with almost none, it runs late.
  • It checks from the inside. Where the server refuses requests to its own address, the checks that need one are marked "Non vérifié" and left out of the score rather than guessed. It does not scan files for malware.

If a command fails

curl: (22) The requested URL returned error: 404

The file name or the version in the URL is wrong. Copy the command again from this page rather than editing the version by hand — and note that curl wrote nothing, so there is nothing to clean up.

WARNING: 1 computed checksum did NOT match

Do not install it. The download was truncated, or it is not the file this page describes. Delete it and download it again; if it fails twice, write to us before running it.

The plugin appears but will not activate

Almost always the PHP version. Every plugin states its minimum above and refuses to run below it rather than failing halfway — check with php -v on the same server.

Several checks say "Non vérifié"

The server refused a request to its own address — a firewall, or a host that blocks loopback calls. Those checks are left out of the score rather than counted as failures. Ask your host to allow the site to reach itself over HTTPS, then scan again.

A quote shows "Échec de l'envoi" in the history

WordPress could not send the e-mail. Set up SMTP or a sending service, then send the request again — or write to us with the reference number from the history page.

Stuck on an install

Send us the command and what it printed.

The output of the command that failed tells us more than a description of it does. Paste it in — there is nothing secret in a download.