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

torchecker

v0.1.7

Published

node package that checks whether a connection is coming from a Tor exit node

Downloads

12

Readme

torchecker

node package that checks whether a connection is coming from a Tor exit node.

To function, torchecker uses an external IP (ideally, this external IP is the IP of your server, it is used to check for exit node policies) you provide and then fetches a list of exit node IPs from

http://exitlist.torproject.org/exit-addresses

and then queries the DNS server ip-port.exitlist.torproject.org.

It refreshes the list of IPs daily.

(This is basically a re-implementation in node.js of the service at

https://check.torproject.org/cgi-bin/TorBulkExitList.py

from

https://svn.torproject.org/svn/check/trunk/cgi-bin/TorBulkExitList.py)

Why

You can expect users connecting through an anonymity network to your site or Internet service are more concerned about their privacy. In the same vein as the Do Not Track Web tracking opt out policies, torchecker allows developers to respect the enhanced privacy expectations of people using the Tor network.

Usage

var torchecker = require('torchecker');

// will remember the EXTERNAL_IP and fetch again once a day
// optional port number as second parameter, otherwise assumes port 80
torchecker.start(EXTERNAL_IP); 
torchecker.stop(); // stop checking once a day, still can be used
console.log(torchecker.check(request.connection)); // returns true if coming through Tor
console.log(torchecker.check("38.229.70.31");
console.log(torchecker.list()); // if you're curious

In the example, torchecker.check should return true if the client IP 38.229.70.31 is Tor traffic contacting your server at the given port.

Learn more

  • https://trac.torproject.org/projects/tor/wiki/doc/TorDNSExitList
  • https://svn.torproject.org/svn/check/trunk/cgi-bin/TorBulkExitList.py