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

@quoin/search-engines

v2.0.1

Published

Utility library to validate IP and UA

Downloads

15

Readme

Quoin - Search Engines utility library

Build Status

This library tries to detect if an access is coming from a search engine.

Basic usage

const searchEngines = require('@quoin/search-engines');

if (searchEngines.match('127.0.0.1', 'Some User Agent')) {
    console.log("This seems to be a search engine.");
} else {
    console.log("This seems to be a normal visit.");
}

API

.get(name)

Gets the search engine defined by name. It returns an instance of SearchEngine.

.listNames()

Gets the list of search engine names. The names can then be used with .get(name) call to get the specific search engine instance.

.match(ipAddress, userAgentString)

Finds if the combination of ipAddress and userAgentString refers to a known search engine. It returns true or false.

.find(ipAddress, userAgentString)

Finds the first search engine instance that matches the combination. The instance of SearchEngine is returned.

Where are the information coming from?

This is a mixed list of manually massaged information from below sites:

  • The list of CIDR comes from Free IP2Location Firewall List by Search Engine

    I've obtained the Apache .htaccess allow file format and hand edited them to only have the CIDR on each line.

  • The user-agent data comes from (https://www.rtcx.net/bot-list)[https://www.rtcx.net/bot-list]

    Only Search Engine are keep for this repo. Some CIDR not present on above source are added from here.