FAQ
Does a finding mean the plugin is broken?#
No. A finding is a pointer for testing. Confidence tells you how sure the scanner is: High means the file is known to load in the editor and the pattern is unambiguous. Confirm findings on a staging copy before reporting them to the plugin author.
Should I run the first scan on staging?#
If you can, yes. The runtime check opens the editor in a simulated state, which runs other plugins’ editor code. A plugin that crashes or exits there is recovered from automatically, but a staging copy is the safest place to find out.
Why is a plugin “Check” from WP-CLI but “Likely broken” in the admin?#
In the admin, the scan sees exactly which files load in the editor. Without that (WP-CLI before any admin scan), it has to guess which files are editor scripts and lowers confidence, and a verdict of Likely broken needs high confidence. Run one scan from Tools → Editor Readiness first.
Does it scan inactive plugins?#
Yes. Every installed plugin is scanned and inactive ones are marked Inactive in the summary, so you can decide before activating them. Only the active theme and its parent are scanned.
Does it scan must-use plugins?#
Only partially. Must-use plugins appear when they register a meta box that the runtime check records; their files are not read.
What about real-time collaboration?#
It is not in a WordPress release yet. Classic meta boxes are not synced, so collaboration will be turned off on posts that show one. A meta box that is safe can pass '__rtc_compatible_meta_box' => true in the add_meta_box() callback arguments. That flag is proposed and may change, which is why these findings are counted as Upcoming.
How long does a scan take on a large site?#
The scan runs in short chunks while the page is open, and in the background (Action Scheduler or WP-Cron) if you close it. Files over 2 MB, large minified files that are not editor scripts, node_modules, .git and test folders are skipped, so even sites with dozens of plugins usually finish in a few minutes.
Where do I enter my license key?#
Under Tools → Editor Readiness License. The plugin scans without a key, but updates and support need an active license.
Does the plugin work without an internet connection to technoleet.dev?#
Yes. Scans are entirely local. The license is re-checked in the background about once a day; if technoleet.dev cannot be reached, a previously valid license keeps working for 14 days.
Can I use it on a local or staging site?#
Yes. License activation is allowed on local and development hosts, so you can test on .test or .local sites. Each activation counts towards your plan’s site limit; deactivate the key when you are done with a temporary site.
How do I get updates?#
Automatically, from technoleet.dev, while the license is active. WordPress shows them on Dashboard → Updates like any other plugin.
Does the plugin send any data anywhere?#
No telemetry. Scan data never leaves your site. The only outbound requests are the license check and the update check to technoleet.dev, which send the license key, the site URL and the plugin version.
Can I scan a site without being an administrator?#
No. Running scans, viewing results and exporting reports all require the manage_options capability.