plugin-health

To check if a plugin is broken or corrupted, verify its integrity by comparing the SHA256 hashes recorded in the installation manifest against the actual files on disk. This detects any tampering or missing files causing the malfunction.

A SHA256 integrity mismatch means the on-disk plugin files have been altered or corrupted since installation, resulting in a broken state. The diagnosis reports this as a sha_mismatch so you can take corrective action like reinstalling.

Run a plugin health check when a plugin appears not to work, after a user reports a bug, or following filesystem migrations and installations. It validates that the installed files still match their recorded integrity hashes to prevent silent failures.

Diagnose a malfunctioning plugin by resolving its slug and calling the health endpoint to check filesystem verification. It returns an actionable diagnosis reporting active, broken with missing files, or sha_mismatch reasons.

Yes, you can detect tampering using filesystem verification by matching manifest-recorded SHA256 hashes against on-disk files. This confirms whether the installation was corrupted or maliciously altered.