Security snapshot
Across 4 processingjs-code-directly WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 4 indexed WordPress sites with processingjs-code-directly, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.5% overall (+17.5 percentage points).
Username enumeration is 50% vs 38.5% overall (+11.5 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected processingjs-code-directly, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
processingjs-code-directly Premium / Custom
This plugin is not available on WordPress.org. It may be a premium plugin, a custom plugin, or a plugin from a third-party marketplace.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| j*n*a*a*i*.com (WP 6.5.10) | F | Aug 30, 2026 | |
| t*i*o*a*d*a*n*.com (WP 4.9.8) | F | Aug 26, 2026 | |
| a*b*y*o*m.com (WP 7.0.4) | F | Aug 17, 2026 | |
| a*-*.com | F | Jul 20, 2026 |