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

zwila-azure-storage

v0.5.1

Published

Use an Azure Storage Account (ASA) as backend for anonymous (but targeted and restricted) file distribution.

Downloads

3

Readme

zwila-azure-storage

JavaScript Style Guide License: Unlicense

Synopsis

npm package to use a single container of an Azure Storage Account (ASA) as backend for anonymous (but targeted and restricted) file distribution.

Data structure in container

  • Top level "folders": blob name prefix, string up to first "/" char, aka slug
    • "Cryptographic" autonaming of folders with nanoid -> hard to guess folder names.
  • Each folder may contain a number of blobs.

Access control

  • The package helps building a proxy webservice that implements access control on the folder level.
    • The ASA container does not need to allow public anonymous access.
    • The package authenticates to the ASA with an access key.
  • On download requests, the proxy generates a short-lived Shared Access Signature (SAS) URL and give it to the anonymous client, which downloads the blob straight from the ASA, without authentication.
  • Folders expire after a number of days (default 31), proxy stops giving access.

Typical use case - hidden download page on your website

  • Use the package to create a folder in the ASA container. Upload files to the folder. Note the generated slug, eg "V1StGXR8_Z5jdHi6B-myT".
  • Have an empty "one-way file transfer" landing page on your website that takes a link ending in a slug, eg https://example.com/transit/V1StGXR8_Z5jdHi6B-myT
  • Use the proxy and package to check if the link is valid and the folder is non-expired, and to list the corresponding files on the landing page. Otherwise leave page empty, or show a message.
  • Distribute the link to persons that shall have anonymous time-limited access to the files within that folder.
  • Persons see the downloads on the landing page, as if stored on your website. On click, they download from Azure.

Usage, API

Todo. For now, study and run the unit tests to see how it works.

Run unit tests

To run the tests in the test/ava directory

  1. Have an Azure Storage Account, and create a container.
  2. Create an .env file in the package root, with these 3 vars:

var | for -|- ZWILA_STORAGEACCOUNT | ASA name ZWILA_ACCESSKEY | ASA access key ZWILA_CONTAINER | name of container for our tests

  1. Run yarn test in the package root.