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

wappalyzer-puppeteer

v0.1.1

Published

Wappalyzer cli using puppeteer as browser

Downloads

24

Readme

Wappalyzer-puppeteer

Wappalyzer-puppeteer is a simple library built on top of Wappalyzer dataset that uncovers the technologies used on websites.

Wappalyzer uses zombie which can handle most websites, but fails on complex / large / js heavy sites.

Since puppeteer is stable and available for many years now, let's use the best of both words, a real browser and Wappalyzer's dataset.

The internal logic is rewritten from scratch, since the original Wappalyzer code has a lot of Promises, on-the-fly regex parsing.

Installation

$ npm i -g wappalyzer-puppeteer      # Globally
$ npm i wappalyzer-puppeteer --save  # As a dependency

There are three main dependencies for this project:

Run from the command line

wappalyzer [url] [options]

Options

--max-wait=ms        Wait no more than ms milliseconds for page resources to load.
--user-agent=str     Set the user agent string.

Run from a script

const { AppAnalytics, PuppeteerCluster, Cluster } = require('wappalyzer-puppeteer');

const url = 'https://www.wappalyzer.com';

const options = {
    maxWait: 5000,
    userAgent: 'Wappalyzer',
    // puppeteerClusterOptions is passed to puppeteer-cluster
    // More options here: https://github.com/thomasdondorf/puppeteer-cluster
    puppeteerClusterOptions: {
        concurrency: Cluster.CONCURRENCY_CONTEXT,
        maxConcurrency: 2,
        puppeteerOptions: {
            headless: true,
            ignoreHTTPSErrors: true
        }
    }
};

const appAnalytics = new AppAnalytics();
const wappalyzer = new PuppeteerCluster(appAnalytics, options);

// Load apps.json (you can provide your own json file as well)
appAnalytics
    .loadAppsjson()
    // start the puppeteer cluster
    .then(() => wappalyzer.startCluster())
    // queue an url and wait for the result
    .then(() => wappalyzer.analyze(url))
    // do whatever you want with the result
    .then(json => {
        process.stdout.write(`${JSON.stringify(json)}\n`);
    })
    // close the cluster
    .then(() => wappalyzer.closeCluster())
    .catch(error => {
        process.stderr.write(`${error}\n`);
        process.exit(1);
    });