The current wappalyzer dataset is kind of unreadable due to size and native json intrinsic unreadability which grows linearly with the size of json. It can be a good occasion to investigate a new implementation and structure the signatures in a folder tree fashion, with a more readable format such as yaml (potentially nuclei templates covering technologies could be reused).
All the signatures must respect the following requirements:
They are based only on passive detection (no request modifiers or additional requests)
They should be idempotent, multiple runs should yield the same result
i found a pretty good source because wappalyzer is not public anymore. https://github.com/tunetheweb/wappalyzer. httpx is also less appropriate for the -td option which does not detect complete due to data reading
The current wappalyzer dataset is kind of unreadable due to size and native json intrinsic unreadability which grows linearly with the size of json. It can be a good occasion to investigate a new implementation and structure the signatures in a folder tree fashion, with a more readable format such as yaml (potentially nuclei templates covering technologies could be reused).
All the signatures must respect the following requirements: