Weston Ruter

Felix Arntz

Google

As <a href="https://developers.google.com/web/updates/2018/09/reportingapi" rel="nofollow ugc">noted on the Google Developers blog</a>:
<blockquote>
The Reporting API defines a new HTTP header, <code>Report-To</code>, that gives web developers a way to specify server endpoints for the browser to send warnings and errors to. Browser-generated warnings like CSP violations, Feature Policy violations, deprecations, browser interventions, and network errors are some of the things that can be collected using the Reporting API.
</blockquote>
This plugin provides a storage mechanism and endpoint for browser reports according to the Reporting API spec in WordPress, as well as an admin interface for browsing these reports. It also provides an API for sending the <code>Report-To</code> response headers.
As the Reporting API specification is still evolving and at an early stage, the plugin reflects that and is currently an experimental prototype, to demonstrate how Reporting API can be used in WordPress.
<h4>Did you know?</h4>
There is also a new specification called Feature Policy which will integrate with the Reporting API specification. There is a <a href="https://wordpress.org/plugins/feature-policy/" rel="ugc">WordPress plugin for Feature Policy</a> as well.

Reporting API

WordPress plugin for receiving browser reports via a Reporting API endpoint.

Jeremy Edmiston

WP-Audit was initially built to provide a detailed audit report of potential client sites. The initial goal was to get as much information about current environment, database, themes and plugins to ensure compatibility within a managed hosting envrionment and for capacity planning.
WP-Audit is part of a full suite of client monitoring and systems health tools currently under development at https://wpsystemcenter.com/

​WP Audit

Provides audit data for site health and client reporting

Reporting API vs ​WP Audit

Reporting API vs WP Audit