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

@shieldsbetter/saferoom

v0.0.1

Published

Generic string escaping.

Readme

We are dead and the web is our hell.

Every service, language, and fever dream has its own restrictions on what characters may appear in its keys, names, and identifiers.

Our sanitization options are a hodge-podge of things that happened to work one time against Apache Server and were eventually enshrined as RFCs.

Sometimes all you want is an invertable process that keeps strings as readable as possible while limiting them to whatever dynamic set of "safe" characters your latest tormentor has saddled you with.

This library does that.

TL;DR

const Saferoom = require('@shieldsbetter/saferoom');

const sr = new Saferoom({
    validCharacters: '_&' + Saferoom.range('0', '9') +
            Saferoom.range('A', 'Z') + Saferoom.range('a', 'z'),
    escapeCharacter: '&'
});

const encoded = sr.encode('key_2006-15-09T06:43:02+9000');

console.log(/^[_&0-9A-Za-z]+$/.test(encoded));  // true
console.log(encoded);  // key_2006&000i&15&000i&09T06&000v&43&000v&02&000g&9000

console.log(sr.decode(encoded));  // key_2006-15-09T06:43:02+9000

Encoded strings meet the following properties:

  • All characters will be from encodingCharacters.
  • Lexicographic comparison of two escape sequences will yield the same order as lexicographic comparison of the original codepoints those escape sequences encode.

Options

The constructor may be provided with a single options object. If this object is omitted, it defaults to {}. The options object may contain the following fields:

  • encodingCodepoints - a string of codepoints that are valid in encoded strings. For convenience we provide the Saferoom.range(a, b) function for generating strings containing all characters between two inclusive codepoints. Default: '_' + Saferoom.range('0', '9') + Saferoom.range('A', 'Z') + Saferoom.range('a', 'z').
  • escapeCodepoint - a single codepoint to be used to set off esape sequences. It is an error for this codepoint to be missing from encodingCodepoints. Default: encodingCodepoints.codePointAt(0).

Note that the encoding format is dynamic based on these parameters and thus the decoder and encoder must be configured the same.