It is important to identify versions of 3rd party tools when describing them.

[mgifford]

Feature/improvement

Axe is described as:

Axe

Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Read more about axe-core.

What version of axe? Latest is 4.7.2

Same with the sniffing tools.

Technologies used to build the page.

Data collected using Wappalyzer. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyser find more information about technologies used.

Data collected using Third Party Web.

Is Third Party Web version 0.24? and what version of Wappalyzer are you running now that the original repo seems to no longer be visible https://github.com/AliasIO/wappalyzer

Also, that link to Wappalyzer will need to be updated.

[soulgalore]

Hi @mgifford , let's add it so we pickup the versions from the package.json file, that should be easy for Axe. For the others coach core needs to expose them, but it should be doable. Do you have time to have a go and make a PR?

Best
Peter

[soulgalore]

Hmm, I checked the code and we actually show the version number for axe on each individual run page:

Let me check if we can add the version number then on the summary page too since it seems to be hard to find.

[soulgalore]

Fot wappalyzer we use https://www.npmjs.com/package/wappalyzer-core and I do not plan to switch to the API in the near future, I haven't looked into how that work.

sitespeedio/coach-core#111 should make it easy to get the versions in the HTML.

[soulgalore]

For upcoming wappalyzer I guess the best way would to go with the fork in https://github.com/HTTPArchive/wappalyzer that way we are inline with HTTPArchive and that seems like a good idea.

[soulgalore]

Versions have been implemented. I'm adding a new issue to switch to https://github.com/HTTPArchive/wappalyzer