GoogleChrome / GoogleChrome/lighthouse-stack-packs

Reliable WordPress detection

Open
#8 18 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
218
Forks
76
PR merge metrics
No merged PRs in 30d

Description

One requirement for adding a stack pack is reliably detecting that the stack/library/platform is being used by the page. We want this detection to be as reliable and bulletproof as possible.

Wappalyzer [uses a few approaches](https://github.com/AliasIO/Wappalyzer/blob/abbb3138be04910765b9b3fe4c988843357288eb/src/apps.json#L11153-L11179) which seem overkill and not something we can reuse. We'd like something much more lightweight.

Primary question: **Can we detect wordpress via via clientside JS running in the page?** (Naturally, it has full access to `window` and the DOM.)

Secondary question: **Is there another reliable detect based on the network request metadata?** We'd like to avoid parsing the response of any network resources (so no looking for patterns in HTML, JS or CSS files). But considering
response headers or paths in urls (like wp-content, etc) is fine.

_Could some WordPress experts chime in?_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.