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.
 
 
 
q-- 9edb79de54
Removed old `libs` dir code from links.cmd
12 years ago
drivers Updated Piwik icon 12 years ago
share Updated Piwik icon 12 years ago
.gitattributes Add .gitattributes files 12 years ago
.gitignore Added package shell script 12 years ago
LICENSE Add correct license information 12 years ago
README.md Added line break to license text 12 years ago
links.cmd Removed old `libs` dir code from links.cmd 12 years ago
links.sh Meta data 12 years ago
package.sh Added Jetpack driver, started converting apps.js to JSON 12 years ago

README.md

Wappalyzer

Wappalyzer is a browser extension that uncovers the technologies used on websites. It detects content management systems, web shops, web servers, JavaScript frameworks, analytics tools and many more.

Contributing

Adding a new application

Example:

"Application Name": { 
	cats:    [ "1" ], 
	headers: { "X-Powered-By": "Application Name" },
	url:     ".+\\.application-name\\.com",
	html:    "<link[^>]application-name\\.css", 
	meta:    { "generator": "Application Name" },
	script:  "application-name\\.js",
	env:     "ApplicationName",
	implies: [ "PHP" ]
	}

Drivers

Wappalyzer is multi-platform. The main code lives in the share/ directory and platform specific code in drivers/. The sections below describe how to set up a development environment for the various existing drivers.

To keep files synchronised between drivers, run the links.sh script (UNIX-like systems only, Windows users can use links.cmd.)

Mozilla Firefox

  • Place a file called wappalyzer@crunchlabz.com in the extensions directory in your profile folder (~/.mozilla/firefox/xxxxx.default/extensions/ on Linux) containing the full path to drivers/firefox.
  • Restart Firefox
  • Navigate to about:config and set extensions.wappalyzer.debug to true.
  • Ctrl+Shift+J brings up a console for debugging.

Google Chrome

The Chrome version needs some love, if anyone wants to pick it up. It's currently not as feature-rich as the Firefox add-on (although partially due to API limitations.)

  • Navigate to about:extensions
  • Check "Developer mode"
  • Click "Load unpacked extension..."
  • Select drivers/chrome/

Bookmarklet

Beta version available for testing at wappalyzer.com/bookmarklet.

HTML

The HTML driver serves purely as an example. It's a good starting point if you want to port Wappalyzer to a new platform.

  • Navigate to drivers/html/

PHP

The PHP driver requires the V8js class. Installing V8js using PECL on Debian Linux or Ubuntu should be very straight forward:

  • # aptitude install php5-dev php-pear libv8-dev
  • # pecl install channel://pecl.php.net/v8js-0.1.3
  • # echo "extension=v8js.so" > /etc/php5/conf.d/v8js.ini

Runnning Wappalyzer from the command line:

$ php drivers/php/index.php wappalyzer.com

Running Wappalyzer inside a PHP script:

require('WappalyzerException.php');
require('Wappalyzer.php');

$wappalyzer = new Wappalyzer($url);

$detectedApps = $wappalyzer->analyze();

Mozilla Jetpack

Work in progress, experimental. See https://wiki.mozilla.org/Jetpack.

Unofficial drivers and ports

Python

A Python driver by @ebradbury.

https://github.com/ebradbury/Wappalyzer/tree/master/drivers/python

Ruby

A Ruby port by @skroutz.

https://github.com/skroutz/wappalyzer-ruby

Screenshot

Wappalyzer on Firefox:

Screenshot

License

Wappalyzer

Copyright © 2012 Elbert Alias and Wappalyzer project contributors

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

A copy of the license is available in the LICENSE file.