Description
Depenova Impact Map is developed by WP Impact Map (https://wpimpactmap.com/).
Depenova Impact Map is a read-only dependency and impact analysis tool for WordPress.
It maps how plugins, themes, must-use plugins and WordPress drop-ins connect to registered functionality and site content. The analysis is based on observed WordPress registrations, source ownership and content references — not a hard-coded list of known plugin names.
What Depenova Impact Map shows
- Component inventory for plugins, themes, must-use plugins and WordPress drop-ins.
- Registered shortcodes, blocks, REST endpoints, AJAX actions, scheduled events and assets.
- Content locations that use detected shortcodes and blocks.
- Component dependencies and semantic enrichment where supported.
- Explainable Impact and Confidence classifications.
- A separate Needs review state when the available evidence is not strong enough.
- Technical evidence for users who want to inspect how a conclusion was reached.
- A read-only disable-impact preview before you make a change.
Built for safe analysis
Depenova Impact Map does not deactivate plugins, modify site content or execute third-party callbacks during analysis.
The Free 0.1.4 release performs its analysis locally. It does not send your dependency map, content relationships or scan evidence to an external service and it does not require WooCommerce, Elementor or any other third-party plugin.
Unknown and custom plugins can still be analysed through the generic WordPress detection engine.
Interface languages
English is the source language. This release also includes Spanish, European Portuguese, French, German, Simplified Chinese, Japanese and Hungarian interface translations. You can follow the WordPress language or select an installed Depenova Impact Map interface language in Settings.
Privacy
Depenova Impact Map performs its Free analysis locally on the WordPress installation and does not send the dependency map, content relationships or scan evidence to an external service.
When content-reference analysis is enabled, the plugin reads WordPress post content and excerpts to identify references to registered shortcodes and blocks. It stores reference metadata such as post IDs, post types and statuses, but does not store full post content in its analysis tables.
Scan results are stored in custom database tables. By default they are preserved if the plugin is deleted. You can enable “Remove Depenova Impact Map data when the plugin is deleted” under Settings before uninstalling if you want those tables and settings removed.
Support
After publication, use the Depenova Impact Map support forum on WordPress.org for Free-version support. Product information and documentation are available at https://wpimpactmap.com/.
Installation
- Upload the
depenova-impact-map-dependency-impact-analysisfolder to/wp-content/plugins/, or install the plugin ZIP through Plugins > Add New > Upload Plugin. - Activate Depenova Impact Map.
- Open Depenova Impact Map > Dashboard in the WordPress admin area.
- Run the first read-only scan.
- Optionally adjust scan scope, interface language and uninstall data retention under Depenova Impact Map > Settings.
FAQ
-
Does Depenova Impact Map change my website?
-
No. The analysis is read-only. It does not deactivate, update or delete plugins, and it does not modify WordPress content.
-
Can Depenova Impact Map tell me that a plugin is definitely safe to delete?
-
No tool can guarantee that for every WordPress configuration. Depenova Impact Map shows detected impact, evidence and confidence. When the available evidence is not strong enough, the component is marked Needs review instead of being presented as safe to remove.
-
Does Depenova Impact Map require WooCommerce or another plugin?
-
No. Third-party plugins are analysed as components. The core analysis engine does not depend on WooCommerce, Elementor or another third-party plugin.
-
Does it work with custom or private plugins?
-
Yes. Generic analysis uses WordPress registrations, callbacks, source ownership and content relationships, so a plugin does not need a dedicated adapter to be included in the map.
-
Does Depenova Impact Map send scan data externally?
-
No. Depenova Impact Map 0.1.4 keeps its dependency map, content relationships and scan evidence on the WordPress installation.
-
What does Needs review mean?
-
It means Depenova Impact Map does not currently have enough evidence to make a confident impact statement. It does not mean the component is broken, unused or safe to remove.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Depenova Impact Map – Dependency & Impact Analysis” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Depenova Impact Map – Dependency & Impact Analysis” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.1.4
- Aligned the translation text domain and self-detection with the final WordPress.org directory slug assigned during approval.
- Cleared the remaining Plugin Check caching warnings for intentional writes to Depenova Impact Map-owned analysis tables.
- Added explicit PHPCS annotations documenting that the mutable scan repository layer does not use the WordPress object cache.
0.1.3
- WordPress.org submission hardening: safer database identifier handling, translator comments, input sanitization and directory-compatible naming.
- Removed the unnecessary manual text-domain loader for WordPress.org-hosted translations.
- Preserved the Depenova Impact Map product branding inside the plugin interface while using a directory-safe listing name and slug.
0.1.2
- Hardened WordPress.org-facing identifiers with a unique plugin prefix.
- Improved uninstall cleanup for temporary scan state and plugin capabilities.
- Improved input handling and translation coverage for admin-facing analysis labels.
- Expanded installation, privacy and support documentation.
0.1.1
- Fixed per-plugin interface language switching so the selected Depenova Impact Map language is applied independently of the WordPress admin language.
- Added consistent English fallback when a selected translation does not contain a string.
0.1.0
- Initial public release.
- Added component inventory, ownership resolution and generic WordPress detectors.
- Added resumable content usage scanning for registered shortcodes and blocks.
- Added the plugin-agnostic Domain Adapter Framework and semantic enrichment layer.
- Added deterministic Impact, Confidence and Needs review analysis.
- Added the read-only Dashboard, Plugins, Needs review, Scans and Settings experience.
- Added scan hardening, parallel-scan protection, permission-aware content locations and configurable scan scope.
- Added interface-language selection and bundled translations for Spanish, European Portuguese, French, German, Simplified Chinese, Japanese and Hungarian.
