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 🙏

© 2026 – Pkg Stats / Ryan Hefner

tofa-server-js

v0.0.1

Published

Tofa adapter for server developers written in javascript

Readme

Javascript Adapter

Use this package if you're developing web apps in javascript.

Include

npm install tofa-server-js

Use

Flow of use:

  1. Initialize with Tor socks5 proxy address
  2. Use adapter methods to communicate with Tofa Clients

Calls are asynchronous.

const {init, reg, info, ask } = require('tofa-server-js')
const TofaErrors = require('tofa-server-js/src/errors')

(async ()=>{
    try {
        /**
        * First initialize adapter with Tor proxy address. Usually it's 127.0.0.1:9050
        * Adapter instance is shared across application, so init should be called only once.
        */
        init('127.0.0.1:9050')

        /**
        * Attempts to register with Tofa Client. 
        * It requires Client URI, and metadata so human can recognize your service.
        * Metadata must contain "name" and "description" (both strings).
        * 
        * @returns: the authentication token which is mandatory when performing ASK and INFO calls.
        *           If any error occurred it will throw an exception exported at 'TofaErrors'
        *
        * Registration process must occur only once, and authentication token
        * must be stored in a database and re-used for eternity.
        */
        let auth_token = await reg(uri, {
            name: "service name",
            description: "service description",
        })

        console.log( 'Auth token:', auth_token )

        /**
        * Attempts to ask for confirmation form Tofa Client amid an action. 
        * It requires Client URI, and metadata so human can recognize the action.
        * Metadata must contain a comprehensive "description" and the "auth_token" (both strings).
        * 
        * @returns: true/false whether human allowed the action or not.
        *           If any error occurred it will throw an exception exported at 'TofaErrors'
        */
        let does_client_allow_action = await ask(uri, {
            description: "Please allow me to perform action X. Will you?",
            auth_token: auth_token,
        })

        console.log( 'did client allow action?: ', does_client_allow_action)
        
        /**
        * Attempts to send an INFO call. This is only a notification sent to the Client.
        * It requires Client URI, and metadata so human can recognize your service.
        * Metadata must contain "name" and "auth_token" (both strings).
        * 
        * @returns: void
        *           If any error occurred it will throw an exception exported at 'TofaErrors'
        */
        await info(uri, {
            description: "Quick info about something. A notification like",
            auth_token
        })

        console.log( 'info sent' )

    }catch(e){
        console.log(e)
        
        /**
        * Exceptions are splitted based on error case.
        * You can take actions based on which error occurred.
        *
        * A full documented list can be browsed within IDE at node_modules/tofa-server-js/src/errors/index.js
        */
        if(e instanceof TofaErrors[...]) 
          console.log(`take this action`)
    }

})();