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

checkmyproxies

v1.0.1

Published

This is a command-line tool for checking the status of SOCKS proxies. The tool takes a list of SOCKS proxies and checks each one to see if it is working or not. The working proxies are saved to a file, and the results are displayed on the console.

Downloads

4

Readme

SOCKS Proxy Checker

This is a command-line tool for checking the status of SOCKS proxies. The tool takes a list of SOCKS proxies and checks each one to see if it is working or not. The working proxies are saved to a file, and the results are displayed on the console.

Features

  • Supports SOCKS version 4 and 5.
  • Checks the status of SOCKS proxies by connecting to a destination address and port.
  • Saves the working proxies to a file.
  • Displays the results on the console.

Installation

To install this tool, you need to have Node.js installed on your system. You can download Node.js from the official website: https://nodejs.org

After installing Node.js, you can install the tool using npm:

npm install -g checkmyproxies

Usage

To use the tool, open a command prompt or terminal and run the following command:

checkmyproxies [options]

Replace [options] with any of the following command-line options:

  • -i, --input: Path to the input file (default: 'proxies.txt').
  • -o, --output: Path to the output file (default: 'working-proxies.txt').
  • -v, --version: SOCKS version (default: 5).
  • -t, --timeout: Connection timeout in milliseconds (default: 5000).
  • -a, --address: Destination address (default: 'www.google.com').
  • -p, --port: Destination port (default: 80).
  • --verbose: Verbose output.
  • -h, --help: Show help message.

Examples

To check a list of SOCKS proxies from a file named proxies.txt and save the working proxies to a file named working-proxies.txt, run the following command:

checkmyproxies

To specify a different input file and output file, run the following command:

checkmyproxies -i input.txt -o output.txt

To check SOCKS version 4 proxies, run the following command:

checkmyproxies -v 4

To set a connection timeout of 10 seconds, run the following command:

checkmyproxies -t 10000

To check the status of the proxies and display the progress on the console, run the following command:

checkmyproxies --verbose

License

This tool is licensed under the GPL3 License. See the LICENSE file for more information.