npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

phantalyzer

v0.1.80

Published

A PhantomJS script for running Wappalyzer over many sites using a headless Webkit browser

Downloads

56

Readme

Overview

Phantalyzer is a PhantomJS (headless Webkit browser bot) based tool that leverages Wappalyzer (browser plugin) to detect software in use across a large number of sites. Wappalyzer is a browser plug-in so it's original design is to provide feedback from within the browser. My intent here is to enable companies to analyze large numbers of sites and provide a report. An example of this would be a report that indicates which sites are using Flash (and may need to be converted), which are not using proper analytics tags, etc.

After getting the Wappalyzer functionality up and running I added a few other features such as image capture for the site, site load time, and breakdown of resources loaded (HTML, CSS, etc).

The basic workflow is that you run the script with a CSV file input that provides sites. The script runs and dumps images out and a resulting json file that contains info about the run. You can then do whatever you want with that data.

Report Script

I also incuded a file called report.php that reads the json file and generates a report of the run across all the sites. I did this in PHP because I'm more comfortable in PHP but that script really should be built in JavaScript. The output would render something that looks like this...

reportimage

Installation

You have to install phantomjs becuase this script depends on it.

Usage

The --sitefile option gives you the ability to specify the csv file for the data. The --maxsites option is used to limit the number of sites visited. Good for testing. The --outputdir option is used to tell Phantalyzer where the result.json file and the images should be stored. The --imgext option is used to tell Phantalyzer which image extension should be used. png and jpg are supported.

phantomjs --web-security=no phantalyzer.js --sitefile sites.csv --maxsites 10 --outputdir ./data --imgext png

Task List

  • [ ] Figure out a way to leverage the Wappalyzer source files upstream rather than copy and paste them here as I've done.
  • [ ] Enable a sophisticated input format that would enable you to specify User Agent and Locale at least on a site by site basis.
  • [ ] Output to a decent format that could be converted to PDF or to Excel.
  • [ ] Create more robust error handling.
  • [ ] Provide a rich set of input options.
  • [ ] Figure out an elegant way to do verbose output for diagnostics.
  • [x] Figure out how to do image captures in a configurable way.