The last commit of Wappalyzer before it went private
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
 
 
 
Alfredo Serafini 4aa28571c0
updating virtuoso detection
8 years ago
bin Merge pull request #1512 from wardoost/default-icon 8 years ago
build Added build folder 10 years ago
docker Add Edge support 8 years ago
src updating virtuoso detection 8 years ago
.editorconfig Added .editorconfig 10 years ago
.gitattributes Fixed merge 12 years ago
.gitignore gitignore Windows and OSX junk files 8 years ago
.travis.yml Add API key to Travis CI configuration 8 years ago
CONTRIBUTING.md Caps lock rocks ;) 9 years ago
LICENSE Add correct license information 12 years ago
README.md Add Scrutinizer badge to README 8 years ago
Vagrantfile Refactoring of wappalyzer validate-icons 10 years ago
schema.json icon optional and defaults to default.svg 8 years ago

README.md

Wappalyzer Travis Scrutinizer

Wappalyzer is a cross-platform utility that uncovers the technologies used on websites. It detects content management systems, eCommerce platforms, web servers, JavaScript frameworks, analytics tools and many more.

Refer to the wiki for screenshots, information on how to contribute and more.

Licensed under the GPL.

Getting Started

This section describes how to set up a development environment. Everything you need is contained in a Docker image which is managed by Vagrant.

Running this environment is optional but recommended as it provides some helpful tools.

First, install Docker and Vagrant on your system.

Clone the Wappalyzer repository and open the newly created directory in a terminal. Run vagrant up to start the environment.

Run vagrant ssh to access the environment and read usage instructions.

$ git clone https://github.com/AliasIO/Wappalyzer.git wappalyzer
$ cd wappalyzer
$ vagrant up
$ vagrant ssh

To stop the environment, run vagrant halt.

If a new Docker image becomes available, rebuild the environment with vagrant destroy -y && vagrant up.