{"id":306299,"date":"2026-05-08T23:17:24","date_gmt":"2026-05-08T23:17:24","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/sentinel-trust-monitor\/"},"modified":"2026-05-11T07:57:29","modified_gmt":"2026-05-11T07:57:29","slug":"sentinel-trust-monitor","status":"publish","type":"plugin","link":"https:\/\/cn.wordpress.org\/plugins\/sentinel-trust-monitor\/","author":23494657,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.4","stable_tag":"1.0.4","tested":"6.9.4","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"Sentinel Trust Monitor","header_author":"DevMuse","header_description":"Know which plugins still deserve your trust. Sentinel Trust Monitor monitors local plugin health, changes, and risk signals directly inside WordPress.","assets_banners_color":"","last_updated":"2026-05-11 07:57:29","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/devmuse.co\/","header_author_uri":"https:\/\/devmuse.co","rating":0,"author_block_rating":0,"active_installs":0,"downloads":193,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.4":{"tag":"1.0.4","author":"devmuse","date":"2026-05-11 07:57:29"}},"upgrade_notice":{"0.9.1":"<p>Repo-checker cleanup package with safe public name, updated headers, and checker-warning reductions.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3526904,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3526904,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.4"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3526904,"resolution":"1","location":"assets","locale":"","width":1200,"height":675},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3526904,"resolution":"2","location":"assets","locale":"","width":1200,"height":675},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3526904,"resolution":"3","location":"assets","locale":"","width":1200,"height":675},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3526904,"resolution":"4","location":"assets","locale":"","width":1200,"height":675}},"screenshots":{"1":"Dashboard with trust score and highest-risk items.","2":"Detail view with verdict, flags, event timeline, and score history.","3":"Settings panel for scheduled scans and email alerts."}},"plugin_section":[],"plugin_tags":[83,8533,5603,600,42414],"plugin_category":[54],"plugin_contributors":[262378],"plugin_business_model":[],"class_list":["post-306299","plugin","type-plugin","status-publish","hentry","plugin_tags-admin","plugin_tags-audit","plugin_tags-monitoring","plugin_tags-security","plugin_tags-trust","plugin_category-security-and-spam-protection","plugin_contributors-devmuse","plugin_committers-devmuse"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/sentinel-trust-monitor\/assets\/icon-128x128.png?rev=3526904","icon_2x":"https:\/\/ps.w.org\/sentinel-trust-monitor\/assets\/icon-256x256.png?rev=3526904","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/sentinel-trust-monitor\/assets\/screenshot-1.png?rev=3526904","caption":"Dashboard with trust score and highest-risk items."},{"src":"https:\/\/ps.w.org\/sentinel-trust-monitor\/assets\/screenshot-2.png?rev=3526904","caption":"Detail view with verdict, flags, event timeline, and score history."},{"src":"https:\/\/ps.w.org\/sentinel-trust-monitor\/assets\/screenshot-3.png?rev=3526904","caption":"Settings panel for scheduled scans and email alerts."},{"src":"https:\/\/ps.w.org\/sentinel-trust-monitor\/assets\/screenshot-4.png?rev=3526904","caption":""}],"raw_content":"<!--section=description-->\n<p>Sentinel Trust Monitor helps you understand whether your installed WordPress plugins still deserve your trust.<\/p>\n\n<p>It detects unexpected changes, explains what they mean, and helps you decide what to do without noise, nags, or unnecessary complexity.<\/p>\n\n<p>Key features:<\/p>\n\n<ul>\n<li>Detect unexpected plugin changes<\/li>\n<li>Understand what changed and why it matters<\/li>\n<li>Mark trusted exceptions for known premium, custom, or agency-built plugins<\/li>\n<li>Keep scan history local and private<\/li>\n<li>Schedule local scans and optional admin email alerts<\/li>\n<\/ul>\n\n<h3>Privacy<\/h3>\n\n<p>Sentinel Trust Monitor 0.9.1 is local-first.<\/p>\n\n<p>The tool stores scan history, metadata, trust scores, events, and settings in the local WordPress database.<\/p>\n\n<p>Sentinel Trust Monitor does not collect visitor data, customer data, form submissions, post content, order data, or personal content.<\/p>\n\n<p>Sentinel Trust Monitor does not send data to a devmuse service in this version.<\/p>\n\n<p>When checking WordPress.org information, the tool may use standard WordPress.org metadata and update information for public repository extensions.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the files to the <code>\/wp-content\/plugins\/sentinel-trust-monitor<\/code> directory, or install the zip through the WordPress Plugins screen.<\/li>\n<li>Activate Sentinel Trust Monitor through the Plugins screen.<\/li>\n<li>Go to Tools \u2192 Sentinel Trust Monitor.<\/li>\n<li>Run your first local scan.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20sentinel%20trust%20monitor%20send%20my%20site%20data%20to%20devmuse%20or%20an%20external%20service%3F\"><h3>Does Sentinel Trust Monitor send my site data to devmuse or an external service?<\/h3><\/dt>\n<dd><p>No. This version is local-first and does not send data to a devmuse service.<\/p><\/dd>\n<dt id=\"does%20it%20use%20wordpress.org%20data%3F\"><h3>Does it use WordPress.org data?<\/h3><\/dt>\n<dd><p>Yes, where available. Sentinel Trust Monitor may use normal WordPress.org metadata and update information for public repository extensions. This is similar to data WordPress already uses for update checks.<\/p><\/dd>\n<dt id=\"is%20this%20a%20security%20plugin%3F\"><h3>Is this a security plugin?<\/h3><\/dt>\n<dd><p>No. Sentinel Trust Monitor is a trust and change visibility layer. It does not replace a firewall, malware scanner, backup system, or security monitoring service.<\/p><\/dd>\n<dt id=\"why%20would%20files%20change%20without%20a%20version%20update%3F\"><h3>Why would files change without a version update?<\/h3><\/dt>\n<dd><p>Possible reasons include manual edits, deployments, host-level changes, failed updates, or unauthorised modification. Sentinel Trust Monitor treats this as worth reviewing because normal updates usually change the version as well.<\/p><\/dd>\n<dt id=\"what%20about%20premium%20or%20custom%20extensions%3F\"><h3>What about premium or custom extensions?<\/h3><\/dt>\n<dd><p>Premium, custom, bundled, or private extensions may not appear on WordPress.org. Sentinel Trust Monitor treats that as a review signal, not proof of danger.<\/p><\/dd>\n<dt id=\"can%20i%20delete%20sentinel%20trust%20monitor%20data%3F\"><h3>Can I delete Sentinel Trust Monitor data?<\/h3><\/dt>\n<dd><p>Yes. Use the Clear Scan History control in the settings area. You can also choose to remove Sentinel Trust Monitor data on uninstall.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.4<\/h4>\n\n<ul>\n<li>Checker-cleanup build for submission.<\/li>\n<li>Removed unused Domain Path header.<\/li>\n<li>Tightened custom-table schema upgrade escaping\/comments.<\/li>\n<li>Added clearer nonce-ignore comments for read-only admin notices.<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>Removed duplicate data\/privacy controls.<\/li>\n<li>Kept uninstall data deletion only in the dedicated Data &amp; Privacy section.<\/li>\n<li>Simplified trusted exception presentation to reduce repeated messaging.<\/li>\n<li>Tidied dashboard settings layout.<\/li>\n<\/ul>\n\n<h4>0.9.6<\/h4>\n\n<ul>\n<li>Added per-item trusted exceptions.<\/li>\n<li>Added Mark as Trusted \/ Remove Trusted Status action on detail views.<\/li>\n<li>Trusted exceptions reduce dashboard and email alert noise while preserving scores, flags, and event history.<\/li>\n<li>Added trusted exception badges in dashboard and inventory views.<\/li>\n<li>Added manual scan error handling with admin feedback.<\/li>\n<li>Added first-scan baseline messaging.<\/li>\n<li>Renamed cleanup section to Data &amp; Privacy.<\/li>\n<li>Updated database schema for trusted exception metadata.<\/li>\n<\/ul>\n\n<h4>0.9.4<\/h4>\n\n<ul>\n<li>Fixed change-detection dashboard ordering so latest scan verdict cards populate correctly.<\/li>\n<li>Added safer manual scan error handling.<\/li>\n<li>Avoided repeated table installation checks on every scan unless the database version is missing or outdated.<\/li>\n<li>Confirmed package naming remains aligned to sentinel-trust-monitor.<\/li>\n<\/ul>\n\n<h4>0.9.3<\/h4>\n\n<ul>\n<li>Restored and clarified the delete-all-data-on-uninstall setting.<\/li>\n<li>Added a dedicated data controls panel.<\/li>\n<li>Improved data retention wording in the dashboard.<\/li>\n<\/ul>\n\n<h4>0.9.2<\/h4>\n\n<ul>\n<li>Fixed scanner parse error introduced during repo-checker cleanup.<\/li>\n<li>Package, folder, and main plugin file now consistently use the sentinel-trust-monitor slug.<\/li>\n<\/ul>\n\n<h4>0.9.1<\/h4>\n\n<ul>\n<li>Repo-checker cleanup package.<\/li>\n<li>Renamed public repository package to Sentinel Trust Monitor to avoid restricted-name warnings.<\/li>\n<li>Updated Tested up to value.<\/li>\n<li>Added languages directory.<\/li>\n<li>Added translator comments for placeholder strings.<\/li>\n<li>Removed dynamic placeholder interpolation from scheduled email query.<\/li>\n<li>Added explicit comments for intentional custom-table database operations.<\/li>\n<\/ul>\n\n<h4>0.9.0<\/h4>\n\n<ul>\n<li>Release-candidate repo-ready package.<\/li>\n<li>Added improved first-run onboarding.<\/li>\n<li>Added clear scan history control.<\/li>\n<li>Added optional data removal on uninstall.<\/li>\n<li>Added fuller WordPress.org readme, FAQ, and privacy wording.<\/li>\n<li>Added plugin header metadata for repository packaging.<\/li>\n<li>Added GPL license file.<\/li>\n<li>General hardening and wording pass.<\/li>\n<\/ul>\n\n<h4>0.8.1<\/h4>\n\n<ul>\n<li>Added human-readable verdict system: Safe, Review, Attention.<\/li>\n<li>Added \"why this matters\" and suggested action guidance.<\/li>\n<li>Improved change interpretation so normal updates are not treated as suspicious file changes.<\/li>\n<li>Added detail-view verdict panel.<\/li>\n<li>Added verdict column to the highest-risk table.<\/li>\n<li>Reduced raw change noise by highlighting unexpected file changes only when the version did not change.<\/li>\n<\/ul>\n\n<h4>0.8.0<\/h4>\n\n<ul>\n<li>Added individual detail view.<\/li>\n<li>Added current risk flag explanations.<\/li>\n<li>Added item-specific event timeline.<\/li>\n<li>Added score history table.<\/li>\n<li>Polished wording around unknown\/premium\/custom items.<\/li>\n<li>Added privacy wording for local-first behaviour.<\/li>\n<\/ul>\n\n<h4>0.7.0<\/h4>\n\n<ul>\n<li>Added settings panel.<\/li>\n<li>Added WP-Cron scheduled scans.<\/li>\n<li>Added daily, twice weekly, weekly, and disabled scan frequency options.<\/li>\n<li>Added optional admin email alerts.<\/li>\n<li>Added alert threshold settings.<\/li>\n<li>Added next scheduled scan display.<\/li>\n<\/ul>\n\n<h4>0.6.0<\/h4>\n\n<ul>\n<li>Added clearer change detection for the latest scan.<\/li>\n<li>Added score-drop events.<\/li>\n<li>Added activation status change events.<\/li>\n<li>Added \"What Changed Since Last Scan\" dashboard panel.<\/li>\n<li>Reduced repeated risk events by recording newly appearing serious flags only.<\/li>\n<\/ul>\n\n<h4>0.5.0<\/h4>\n\n<ul>\n<li>Added Sentinel column to the installed extensions screen.<\/li>\n<\/ul>\n\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>Added WordPress.org intelligence.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>Added local trust scoring engine.<\/li>\n<li>Added status bands: Healthy, Watch, Review, Risky.<\/li>\n<li>Added highest-risk dashboard panel.<\/li>\n<li>Added recent local signals timeline.<\/li>\n<li>Improved dashboard styling.<\/li>\n<\/ul>\n\n<h4>0.2.0<\/h4>\n\n<ul>\n<li>Added local scanner and database snapshots.<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>Initial dashboard shell and activation tables.<\/li>\n<\/ul>","raw_excerpt":"Know which installed extensions still deserve your trust.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/306299","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=306299"}],"author":[{"embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/devmuse"}],"wp:attachment":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=306299"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=306299"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=306299"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=306299"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=306299"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=306299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}