{"id":370911,"date":"2026-09-22T15:59:18","date_gmt":"2026-09-22T15:59:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/m7tawa-impact-monitor\/"},"modified":"2026-09-22T15:58:43","modified_gmt":"2026-09-22T15:58:43","slug":"m7tawa-impact-monitor","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/m7tawa-impact-monitor\/","author":23549527,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"2.8.3","stable_tag":"2.8.3","tested":"7.1.2","requires":"6.5","requires_php":"7.4","requires_plugins":null,"header_name":"M7tawa Impact Monitor","header_author":"Ayman Abdullah","header_description":"Track plugin lifecycle impact with read-only scores, timelines, update comparisons, residue checks, and dependency evidence.","assets_banners_color":"313e51","last_updated":"2026-09-22 15:58:43","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/m7tawa.com\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":49,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"2.8.3":{"tag":"2.8.3","author":"aymanabdullahdev","date":"2026-09-22 15:58:43","revision":3707708}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3707713,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3707713,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3707713,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3707713,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.8.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3707721,"resolution":"1","location":"assets","locale":"","width":1400,"height":841},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3707721,"resolution":"2","location":"assets","locale":"","width":1400,"height":809},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3707721,"resolution":"3","location":"assets","locale":"","width":1400,"height":718}},"screenshots":[]},"plugin_section":[],"plugin_tags":[4567,153,23519,282089,23853],"plugin_category":[59],"plugin_contributors":[275923],"plugin_business_model":[],"class_list":["post-370911","plugin","type-plugin","status-publish","hentry","plugin_tags-cron","plugin_tags-database","plugin_tags-diagnostics","plugin_tags-impact-monitor","plugin_tags-rest-api","plugin_category-utilities-and-tools","plugin_contributors-aymanabdullahdev","plugin_committers-aymanabdullahdev"],"banners":{"banner":"https:\/\/ps.w.org\/m7tawa-impact-monitor\/assets\/banner-772x250.png?rev=3707713","banner_2x":"https:\/\/ps.w.org\/m7tawa-impact-monitor\/assets\/banner-1544x500.png?rev=3707713","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/m7tawa-impact-monitor\/assets\/icon-128x128.png?rev=3707713","icon_2x":"https:\/\/ps.w.org\/m7tawa-impact-monitor\/assets\/icon-256x256.png?rev=3707713","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/m7tawa-impact-monitor\/assets\/screenshot-1.png?rev=3707721","caption":""},{"src":"https:\/\/ps.w.org\/m7tawa-impact-monitor\/assets\/screenshot-2.png?rev=3707721","caption":""},{"src":"https:\/\/ps.w.org\/m7tawa-impact-monitor\/assets\/screenshot-3.png?rev=3707721","caption":""}],"raw_content":"<!--section=description-->\n<p>M7tawa Impact Monitor is a lightweight, event-based diagnostic tool for WordPress administrators and developers.<\/p>\n\n<p>Version 2.8.3 remains read-only for site and extension data. It does not delete tables, remove options, disable assets, or change WordPress settings.<\/p>\n\n<p>Version 2 adds detailed before\/after evidence instead of summary counts alone.<\/p>\n\n<p>Features:<\/p>\n\n<ul>\n<li>Create a manual baseline of the current site.<\/li>\n<li>Record measurable changes after extension installation, activation, deactivation, updates, and successful deletion.<\/li>\n<li>Show a per-extension Lifecycle Timeline with event filtering, version transitions, and first\/last monitored dates.<\/li>\n<li>Show exact names of added and removed database tables, cron hooks, post types, taxonomies, and REST routes.<\/li>\n<li>Index option metadata without copying option values: option name, autoload state, and byte size only.<\/li>\n<li>Skip detailed option indexing automatically on sites with more than 20,000 options to keep scans conservative; autoload total remains available.<\/li>\n<li>Show added, removed, and size\/autoload-changed options after a version 2 baseline.<\/li>\n<li>Show role and capability changes.<\/li>\n<li>Show version transitions for monitored updates when available.<\/li>\n<li>Provide an impact profile for every installed extension, while clearly marking extensions that only exist in the baseline.<\/li>\n<li>Preserve v1.x history during upgrade.<\/li>\n<li>Require explicit confirmation before clearing the monitor's own history.<\/li>\n<li>Load no frontend CSS or JavaScript.<\/li>\n<li>Keep only the latest 100 monitoring events.<\/li>\n<li>Calculate a transparent 0\u2013100 Impact Score from attributable observed evidence only.<\/li>\n<li>Show Low, Moderate, High, or Very High technical impact without labeling extensions as good, bad, safe, or unsafe.<\/li>\n<li>Break the score into Database, Runtime, WordPress Integration, and Footprint Breadth components.<\/li>\n<li>Label partial scores when activation was not observed and leave baseline-only extensions unscored.<\/li>\n<li>Show Impact Score before\/after observed events and version updates.<\/li>\n<li>Distinguish Current Impact Score from Peak Impact Score and show signed Event Impact Delta.<\/li>\n<li>Keep a compact observed score history with Rising, Falling, Stable, or New history trend labels.<\/li>\n<li>Show the top score contributors and conservative Attention Flags that explain what may deserve manual review.<\/li>\n<li>Show a dedicated before\/after score comparison for monitored updates and highlight notable score shifts of 10 points or more.<\/li>\n<li>Show Observed or Partial confidence directly beside scored extension profiles.<\/li>\n<li>Filter and sort extension profiles by impact level or score.<\/li>\n<li>Use cron recurrence metadata when available so high-frequency schedules contribute more than infrequent schedules.<\/li>\n<li>Never take automatic action based on a score.<\/li>\n<li>After a successful extension deletion, run a read-only Residue Monitor check for remaining tables, options, transients, cron hooks, roles, post meta keys, and user meta keys.<\/li>\n<li>Separate Observed residue from lower-confidence Likely related naming evidence instead of claiming uncertain ownership.<\/li>\n<li>Recheck a stored residue report manually without deleting or modifying any site data.<\/li>\n<li>Build a per-extension Dependency Map from the WordPress Requires Plugins header, reverse dependents, observed shared-resource evidence, and monitored footprint evidence.<\/li>\n<li>Keep declared dependency metadata separate from observed integration evidence so shared resources are never presented as proof of dependency.<\/li>\n<\/ul>\n\n<p>The monitor uses on-demand and event-based scans. It does not run heavy diagnostic scans on ordinary frontend page loads.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin to <code>\/wp-content\/plugins\/m7tawa-impact-monitor\/<\/code> or install the ZIP from WordPress admin.<\/li>\n<li>Activate the plugin.<\/li>\n<li>Go to Tools &gt; Impact Monitor.<\/li>\n<li>Create a version 2 baseline when prompted.<\/li>\n<li>Future install, activation, deactivation, update, and deletion events will include lifecycle history and detailed before\/after information.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"what%20does%20impact%20score%20mean%3F\"><h3>What does Impact Score mean?<\/h3><\/dt>\n<dd><p>Impact Score is a technical footprint indicator from 0 to 100. It is based on attributable observed evidence such as tables, option metadata, autoload growth, cron hooks and recurrence, REST routes, content types, taxonomies, roles, and capabilities. A higher score does not mean an extension is bad or unsafe; feature-rich extensions can naturally have a larger footprint.<\/p><\/dd>\n<dt id=\"why%20is%20a%20score%20marked%20partial%3F\"><h3>Why is a score marked Partial?<\/h3><\/dt>\n<dd><p>The monitor observed some attributable changes but did not observe the extension from activation, so it cannot claim a complete footprint. Baseline-only extensions remain unscored.<\/p><\/dd>\n<dt id=\"does%20it%20delete%20anything%3F\"><h3>Does it delete anything?<\/h3><\/dt>\n<dd><p>No. Version 2.8.3 is read-only for site and extension data.<\/p><\/dd>\n<dt id=\"does%20it%20store%20option%20values%3F\"><h3>Does it store option values?<\/h3><\/dt>\n<dd><p>No. It stores only option names, autoload state, and byte size so it can compare metadata without duplicating option contents.<\/p><\/dd>\n<dt id=\"does%20residue%20monitor%20delete%20leftovers%3F\"><h3>Does Residue Monitor delete leftovers?<\/h3><\/dt>\n<dd><p>No. Residue Monitor only detects, attributes, explains, and rechecks what remains after an extension is removed. Observed residue means the item was introduced during a monitored event and still exists after removal. Likely related means the current item matches extension-specific naming evidence, but ownership is not claimed as certain.<\/p><\/dd>\n<dt id=\"how%20does%20dependency%20map%20decide%20that%20extensions%20are%20related%3F\"><h3>How does Dependency Map decide that extensions are related?<\/h3><\/dt>\n<dd><p>Declared dependencies come directly from the WordPress Requires Plugins header. The monitor can also show exact resource names observed with more than one extension, but those are labeled as shared-resource evidence only and are never treated as proof that one extension depends on another.<\/p><\/dd>\n<dt id=\"does%20it%20add%20scripts%20to%20the%20frontend%3F\"><h3>Does it add scripts to the frontend?<\/h3><\/dt>\n<dd><p>No. Admin assets load only on the monitor screen.<\/p><\/dd>\n<dt id=\"why%20do%20some%20extensions%20say%20baseline%20only%3F\"><h3>Why do some extensions say Baseline only?<\/h3><\/dt>\n<dd><p>Those extensions were already present when the baseline was created and no activation, deactivation, or update event has been observed for them yet. The monitor does not guess ownership.<\/p><\/dd>\n<dt id=\"what%20is%20observed%3F\"><h3>What is Observed?<\/h3><\/dt>\n<dd><p>Observed means the monitor was present when the event occurred and could compare site state around that event.<\/p><\/dd>\n<dt id=\"what%20happens%20to%20my%20version%201%20history%3F\"><h3>What happens to my version 1 history?<\/h3><\/dt>\n<dd><p>It is preserved. Run a new version 2 baseline once to enable detailed option and role comparison for future events.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>2.8.3<\/h4>\n\n<ul>\n<li>Exclude known WordPress updater process transients, the cron storage option, and updater cleanup cron noise from extension attribution and Impact Score.<\/li>\n<li>Show excluded WordPress update process changes separately for transparency.<\/li>\n<li>Force left-to-right version flows so Before \u2192 After is displayed correctly in RTL dashboards.<\/li>\n<li>Harden Update Watch across more WordPress update flows.<\/li>\n<li>Capture pre-update state from both pre-download and pre-install upgrader hooks when available.<\/li>\n<li>Add a read-only admin fallback that detects missed plugin version changes on the next admin request and records an Updated event automatically.<\/li>\n<li>Preserve explicit attribution limits for batch or fallback-detected updates.<\/li>\n<\/ul>\n\n<h4>2.8.0<\/h4>\n\n<ul>\n<li>Added Dependency Map with declared Requires Plugins relationships, reverse dependents, observed shared-resource evidence, and per-extension footprint evidence.<\/li>\n<li>Dependency relationships are separated by confidence: declared metadata is authoritative; shared resources are integration evidence only.<\/li>\n<\/ul>","raw_excerpt":"Monitor measurable extension impact on WordPress without deleting or changing site data.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/370911","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=370911"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/aymanabdullahdev"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=370911"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=370911"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=370911"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=370911"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=370911"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=370911"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}