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

@nicholasfulton/auth_accessor

v2.0.4

Published

To build, run `npm install` followed by `npm run build` in the project directory. These commands will build the output module, in the auth directory. At this point the auth directory is ready to be moved to its destination.

Readme

Auth Accessor

Building

To build, run npm install followed by npm run build in the project directory. These commands will build the output module, in the auth directory. At this point the auth directory is ready to be moved to its destination.

Usage

Keys

In the root of the repository, keys.txt contains development keys for authenticating servers. In production, unique credentials will be generated with various scopes.

Setup

Place the auth folder in the project directory. Include a reference to accessor.js, a direct child of the auth directory. This contains a class definition which implements the interface defined in iaccessor.js. Its constructor accepts the server ID and server secret as parameters.

Example:

const auth = new (require('./auth/accessor').Accessor)(serverId, serverSecret);

// or 

const Accessor = require('./auth/accessor').Accessor;
const auth = new Accessor(serverId, serverSecret);

// use auth...

Check Session

This will check whether a user's session is valid without extending its duration or updating the user cookie (refreshing). The required parameters are the session ID and token which are encoded in the MDXS (Munidex session) cookie in the form {sessionId}:{sessionToken}.

Example:

// ...initialize auth

auth.isSessionValid(id, token).then(isValid => {
    if (isValid) {
        console.log("Session is valid!");
    }
    else {
        console.log("User needs to be redirected to signin");
    }
});

// or

let isValid = await auth.isSessionValid(id, token);
console.log(isValid ? "Session is valid!" : "User needs to be redirected to signin");

Refresh Session

Similar to check session, but the expiration timestamp on the session is to be extended both on database and in the user cookie. Not yet implemented.

Get User Info

This will, if a user's session is valid retreive a user's profile from the auth server using their session ID. In the future an option to retreive their profile offline, using their unique ID, will be added.

IMPORTANT: the current implementation retrieves the user info by their session ID rather than user ID

Example:

// ...initialize auth

auth.getUserInfo(id).then(profile => {
    console.log(profile);
}).catch(err => {
    console.log(err); // Most likely user is not signed in
});

// or

let profile = await auth.getUserInfo(id);