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

dangoco

v0.3.7

Published

A proxy over websocket

Downloads

5

Readme

dangoco

(団子子) A proxy over websocket

node.js^7.5.0 is required. Don't have?

Using

npm i -g dangoco

Client

dangocoClient [options]

#see --help for options

#example
dangocoClient -s ws://example.com/xxx -u dango -p test --socksHost 0.0.0.0 --socksPort 1080  -a aes-256-cfb
# --socksHost 0.0.0.0			start a client listening on 0.0.0.0:1080 for socks connections 
# --socksPort 1080
# -s ws://example.com/xxx		and use ws://example.com/xxx as the proxy server
# -u dango -p test				the username is dango and the password is test
# -a aes-256-cfb				using an encryption algorithm aes-256-cfb cause it is an insecure connection
#								wss(websocket over https) is recommended,or the inspector may recognize your proxy(including url and websocket tunnel control frames)

Server

dangocoServer [options]

#see --help for options

#example
dangocoServer -u '[["dango","test"]]' -L
# -u '[["dango","test"]]'	set a json with users in it
# -L						display logs(for debug)
# the server listens on 127.0.0.1:80 by default.You can set -h host -p port to specify it.

Supported protocol

  • TCP
  • UDP