Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.13MB] [CPU: ▼1.26ms] Passed 4 tests
This is a short check of server-side resources used by Vulners Scanner
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.59 ▲0.12 | 38.28 ▲2.09 |
| Dashboard /wp-admin | 3.44 ▲0.13 | 49.19 ▲1.66 |
| Posts /wp-admin/edit.php | 3.55 ▲0.19 | 45.87 ▼0.24 |
| Add New Post /wp-admin/post-new.php | 6.04 ▲0.15 | 86.51 ▼8.55 |
| Media Library /wp-admin/upload.php | 3.36 ▲0.13 | 42.03 ▲9.61 |
| Vulners Scanner /wp-admin/admin.php?page=vulners-scanner/scanner.php | 3.33 | 31.11 |
| Vulners Settings /wp-admin/admin.php?page=vulners-settings | 3.33 | 30.36 |
Server storage [IO: ▲5.29MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 10 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| vulners_os_audit_result |
| vulners_os_audit_last_changes |
| vulners_plugins_audit_last_changes |
| widget_recent-posts |
| vulners_plugins_audit_result |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
Vulners Scanner: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,843 ▲82 | 22.82 ▲8.26 | 1.64 ▼0.04 | 45.48 ▲4.66 |
| Dashboard /wp-admin | 2,252 ▲72 | 13.79 ▲8.12 | 296.01 ▲207.76 | 81.49 ▲41.68 |
| Posts /wp-admin/edit.php | 2,154 ▲54 | 11.25 ▲9.23 | 136.74 ▲101.84 | 41.31 ▲8.91 |
| Add New Post /wp-admin/post-new.php | 1,569 ▲41 | 32.89 ▲9.72 | 663.32 ▼23.76 | 29.70 ▼27.66 |
| Media Library /wp-admin/upload.php | 1,451 ▲51 | 13.11 ▲8.86 | 199.94 ▲103.52 | 73.24 ▲26.85 |
| Vulners Scanner /wp-admin/admin.php?page=vulners-scanner/scanner.php | 1,003 | 12.84 | 229.08 | 43.67 |
| Vulners Settings /wp-admin/admin.php?page=vulners-settings | 856 | 10.84 | 126.67 | 25.86 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 3× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/vulners-scanner/index.php
- > /wp-content/plugins/vulners-scanner/templates/report.php
- > /wp-content/plugins/vulners-scanner/scanner.php
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please fix the following browser errors
- > GET request to /wp-admin/admin.php?page=vulners-scanner/scanner.php
- > Network (severe)
wp-admin/admin-ajax.php - Failed to load resource: the server responded with a status of 403 (Forbidden)
- > GET request to /wp-admin/admin.php?page=vulners-scanner/scanner.php
- > Console-api (warning) in unknown
webpack://vulners-wp-plugin/./node_modules/mobx/dist/mobx.esm.js? 1826:107 "[MobX] Since strict-mode is enabled, changing (observed) observable values without using an action is not allowed. Tried to modify: ScanStore@1.pluginsError"
- > GET request to /wp-admin/admin.php?page=vulners-scanner/scanner.php
- > Console-api (warning) in unknown
webpack://vulners-wp-plugin/./node_modules/mobx/dist/mobx.esm.js? 1826:107 "[MobX] Since strict-mode is enabled, changing (observed) observable values without using an action is not allowed. Tried to modify: ScanStore@1.pluginsLoading"
- > GET request to /wp-admin/admin.php?page=vulners-scanner/scanner.php
- > Console-api (warning) in unknown
webpack://vulners-wp-plugin/./node_modules/mobx/dist/mobx.esm.js? 1826:107 "[MobX] Since strict-mode is enabled, changing (observed) observable values without using an action is not allowed. Tried to modify: ScanStore@1.pluginsLastScan"
- > GET request to /wp-admin/admin.php?page=vulners-settings
- > Javascript (severe) in unknown
webpack://vulners-wp-plugin/./node_modules/react-dom/cjs/react-dom.development.js? 26085:12 Uncaught Error: Target container is not a DOM element.
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
2 plugin tags: external, vulnerability assessment
vulners-scanner/index.php 85% from 13 tests
The main file in "Vulners Scanner" v. 1.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Description: Please keep the plugin description shorter than 140 characters (currently 236 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("vulners-scanner.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin2,548 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 230 | 210 | 1,334 |
| JavaScript | 1 | 694 | 733 | 1,209 |
| SVG | 1 | 0 | 0 | 5 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 13.00 |
| ▷ Minimum class complexity | 5.00 |
| ▷ Maximum class complexity | 28.00 |
| Average method complexity | 3.36 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 13 | |
| ▷ Static methods | 3 | 23.08% |
| ▷ Public methods | 11 | 84.62% |
| ▷ Protected methods | 2 | 15.38% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 33 | |
| ▷ Named functions | 24 | 72.73% |
| ▷ Anonymous functions | 9 | 27.27% |
| Constants | 6 | |
| ▷ Global constants | 1 | 16.67% |
| ▷ Class constants | 5 | 83.33% |
| ▷ Public constants | 5 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin