pteglia

PillarShield integrates WordPress with the PillarShield SaaS governance API. It runs checks at the publish boundary, blocks non‑compliant content, allows optional overrides, and keeps a governance record per post for reporting. You must obtain a PillarShield API key from https://pillarshield.co for the plugin to function.
Key features:
<ul>
<li>Gate governance checks on publish/private statuses (configurable per post type).</li>
<li>Optional manual checks that never block saves.</li>
<li>Override workflow for privileged users.</li>
<li>Governance reporting under Tools → PillarShield (blocked-at-gate items only).</li>
<li>Safe storage of outcomes without raw content.</li>
</ul>
<h3>Configuration</h3>
Settings → PillarShield:
<ul>
<li>API Endpoint: The PillarShield governance endpoint.</li>
<li>API Key: Your tenant API key (<code>psk_...</code>).
<ul>
<li>Get a key at https://pillarshield.co. The plugin does not perform governance checks without a valid API key.</li>
<li>You can also define <code>PILLARSHIELD_API_KEY</code> in <code>wp-config.php</code> to override the stored option: 
define(‘PILLARSHIELD_API_KEY’, ‘psk_…’);</li>
</ul>
</li>
<li>Enable Governance: Turn checks on/off.</li>
<li>Allow Save Without API: Allow publishing if the API is unavailable.</li>
<li>Enabled Post Types: Which post types are governed.</li>
<li>Fields per Post Type: Comma‑separated fields to scan. Supports <code>meta:KEY</code>.</li>
<li>Gate Configuration:
<ul>
<li>Gated statuses (default: publish + private)</li>
<li>Fallback status (default: draft)</li>
</ul>
</li>
</ul>
Use the Test Connection button to validate API access.
<h3>Editor UX</h3>
On governed post types, a PillarShield meta box appears with:
<ul>
<li>Check PillarShield governance on this save (manual check)</li>
<li>Override PillarShield governance (save anyway)</li>
</ul>
These checkboxes do not persist — they only apply to the current save.
<h3>Permissions (Roles/Capabilities)</h3>
PillarShield adds these capabilities:
<ul>
<li><code>pillarshield_manage_settings</code> — manage settings page</li>
<li><code>pillarshield_view_reports</code> — view reports</li>
<li><code>pillarshield_manual_check</code> — run manual check</li>
<li><code>pillarshield_override_governance</code> — override violations</li>
</ul>
On activation, these are granted to Administrators only.
Override visibility requirement: 
The Override checkbox only appears for users who have the <code>pillarshield_override_governance</code> capability. Editors will not see it unless you explicitly grant that capability via a role editor plugin or custom code.
<h3>Reporting</h3>
Tools → PillarShield:
<ul>
<li>Overview of content currently blocked at the gate.</li>
<li>Details page per post with block reason and metadata.</li>
</ul>
<h3>External services</h3>
This plugin connects to the PillarShield governance API to evaluate post content for compliance before publishing.
Service: PillarShield SaaS governance API, operated by PillarShield. 
Endpoint: https://api.pillarshield.co/pillarshield-governance/governance
What is sent and when: 
When a user saves a post to a gated status (by default: publish or private) on a governed post type, or manually triggers a governance check, the plugin sends a POST request containing:
<ul>
<li>The post’s configured content fields (by default: title, body, and excerpt)</li>
<li>Post metadata: post type, post ID, post UUID, post URL, and target publish status</li>
<li>WordPress user context: user ID and roles (no email or username is transmitted)</li>
<li>The tenant API key</li>
</ul>
No data is sent during autosaves, revisions, or saves to non-gated statuses. The plugin requires a valid API key obtained from https://pillarshield.co to function.
<ul>
<li><a href="https://pillarshield.co/terms" rel="nofollow ugc">Terms of service</a></li>
<li><a href="https://pillarshield.co/privacy-policy" rel="nofollow ugc">Privacy policy</a></li>
</ul>
<h3>Support</h3>
Support and documentation: https://pillarshield.co.

PillarShield

Connect WordPress to the PillarShield SaaS API and enforce governance checks at publish time.

Malcolm Peralty

Governance Guardrails is a file-based WordPress governance plugin for site owners, agencies, and managed WordPress teams that want important operational rules to live in code instead of scattered database settings.
You define a policy in a PHP configuration file. Governance Guardrails reads that file on each request and applies the configured rules. This makes the policy easy to review, version-control, and deploy consistently across environments or multiple sites.
Governance Guardrails can help you manage:
<ul>
<li>Feature toggles such as XML-RPC, comments, feeds, the Customizer, widgets, application passwords, user registration, WP-Cron, and related admin features.</li>
<li>Admin UI cleanup, including admin bar nodes, dashboard widgets, menu pages, and admin footer text.</li>
<li>Runtime capability denials by role without changing stored role definitions in the database.</li>
<li>Upload governance, including allowed MIME types and per-file size limits.</li>
<li>Content behavior such as revisions, autosave intervals, oEmbed, and emoji loading.</li>
<li>Login behavior such as password reset restrictions, generic login errors, and post-logout redirects.</li>
<li>HTTP security headers and other hardening options such as pingback removal, author archive handling, file editing restrictions, and staging noindex headers.</li>
<li>Head cleanup for RSD, WLW manifest, shortlinks, feed links, and REST API discovery links.</li>
<li>Locked options so selected <code>wp_options</code> values are pinned from code.</li>
<li>Custom governance callbacks for site-specific rules.</li>
</ul>
This plugin does not claim to secure a site by itself. It is intended as a governance and consistency tool that helps keep selected WordPress settings and behaviors aligned with your site’s operational policy.
<h4>Must-use plugin support</h4>
Governance Guardrails was originally built for must-use plugin deployment. It can still be installed that way by copying <code>governance-guardrails.php</code> and the <code>governance-guardrails/</code> directory into <code>wp-content/mu-plugins/</code>.
For WordPress.org installation, it can also be installed and activated as a normal plugin. In that case, the included sample config is used from the plugin directory unless you define a custom config path.
To use a custom config file, add this to <code>wp-config.php</code>:
<pre><code>define( 'GOVGUARD_CONFIG', '/absolute/path/to/governance-guardrails-config.php' );
</code></pre>
The shipped sample config lives at <code>governance-guardrails/governance-guardrails-config.php</code>.
Config loading is fail-open. If the config file is missing, unreadable, has a syntax error, or does not return an array, Governance Guardrails does not enforce governance rules and logs a warning instead of crashing the site.
<h4>WP-CLI</h4>
When WP-CLI is available, Governance Guardrails registers the <code>wp governance</code> command set.
Examples:
<ul>
<li><code>wp governance status</code></li>
<li><code>wp governance check</code></li>
<li><code>wp governance audit</code></li>
<li><code>wp governance audit --severity=high</code></li>
<li><code>wp governance diff</code></li>
<li><code>wp governance get features --format=json</code></li>
<li><code>wp governance mimes</code></li>
</ul>

Governance Guardrails

Governance Guardrails provides file-based rules for managing admin behavior, capabilities, uploads, and operational hardening from code.

PillarShield vs Governance Guardrails