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

canonical-base64

v1.1.0

Published

test wether a base64 string will serialize the same after parsing

Downloads

10

Readme

is-canonical-base64

a regular expression to test wether a string is a valid base64, without ambiguity.

note npm has implemented a (badly working) spam filter which disallowed me to publish is-canonical-base64 so this is published as reversable-base64 and canonical-base64 (I'd much prefer is- at the start however, because the purpose of this module is a boolean test. And "is" turns it into a yes/no name)

Base64 encodes bytes (base 256, 8 bits each) as chars each representing 6 bits. That means a one byte buffer necessarily becomes 2 chars, except only the top 2 bits of the last char are used (and the string is then padded with an == to take the spaces those chars would be)

It's recommended that implementations encode zeros here, but many implementations (including node.js's) accept non-zeros here, but just ignore them.

This can be a problem for signed data, because if the signature signs base64, you must retain exactly the encoded representation (including any ambiguity). So, it's good to enforce that ambigious representations are rejected.

usage

simple

var isCanonicalBase64 = require('canonical-base64')() //note, returns a function
isCanonicalBase64.test(string)

advanced: you may pass in a prefix and suffix, which is combined into the regular expression.

var isCanonicalBase64 = require('canonical-base64')('@', '(?:\.ed25519)')
isCanonicalBase64.test(string)

License

MIT