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 🙏

© 2025 – Pkg Stats / Ryan Hefner

abase

v1.0.0

Published

A simple service to help people manage their personal data in your app.

Readme

abase ("a Base")

A Base for building reliable web apps quickly.

Why?

Keeping people's (personal) data safe is essential in every web application that requires personalisation. Yet writing the code to help people manage their own data can be quite tedious and usually is not the "core competence" of most web apps.

We found that we had built/re-built the "user" registration/verification/login, "manage my profile/preferences" and permissions/roles "workflow" enough times that it was time to make something generic & re-useable.

You can pay a 3rd Party "Auth"-as-a-Service Provider and have them manage your ("user") data on a server you have no control over and pay them for each registration/login event ... for some companies this is a good option because they don't have to think about where the data is stored, however we prefer to know exactly where data is stored, how it's encrypted and who can access it.˜

What?

Distinguishing/Differntiating Features

  • A Secure way of storing people's personal data.
  • Plain English Access controls
  • Mobile First/Optimised (Responsive) UI (view/edit data on any device)
  • Server-side Rendered (for speed) with client-side (progressive) enhancement (for user experience)

Who?

Who Should Use This?

Anyone building a web app (where the experience is personalised) and wants to know where/how data is stored and thus ensure that customer data is not being miss-managed or sold (which we think wrong).

How?

Requirements

  • Simple UI/UX for people to
    • register
    • login
    • verify (their email)
    • re-set password
    • view/update any other personal details once logged in
  • REST API Endpoint for all actions (when content-type is not set to text/html)
  • HTML Responses for all endpoints that request content-type

tl;dr

Why Build a New Tool/Service?

There are many platforms for "User" (people) authentication and personal data storage/management, why build another one?

Simple: to incorporate the all the best ideas/practices we like and have an extensible (plugin-based) platform anyone can add to/build upon.

Why PostgreSQL?

While there is a lot of hype surrounding NoSQL Databases like MongoDB & Redis, we found we were having to write a lot of code to do useful queries. And while de-normalising data might "make sense" for "scalability" in theory, what we found in practice is that even with 100 Billion Records (way more users than 99.99% of companies/startups!) a well-managed PostgreSQL cluster copes very well.

Make up your own mind: https://www.postgresql.org/about
If you're still Curious or Worried about scaling PostgreSQL? see: https://www.citusdata.com Want to model the network of people as a graph? https://github.com/cayleygraph/cayley