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

@liteeagle226/browser

v0.1.1

Published

Zero-build browser bundle for the Vallum SDK

Downloads

265

Readme

@liteeagle226/browser

Use Vallum from regular HTML and JavaScript without a bundler. CSS does not run network or cryptographic code, so a small JavaScript module is still required; the page and styling can otherwise remain framework-free.

Install

For a bundler-based application, install the browser package. Its @liteeagle226/client dependency is installed automatically:

npm install @liteeagle226/browser

For a no-build page, use one of the version-pinned CDN entries below. Either frontend needs a trusted backend broker from @liteeagle226/admission (or the server entry in @liteeagle226/nextjs).

Classic script

Pin an exact version in production and apply your normal Content Security Policy and Subresource Integrity process:

<pre id="result" aria-live="polite">Loading…</pre>
<script src="https://cdn.jsdelivr.net/npm/@liteeagle226/[email protected]/dist/vallum.iife.js"></script>
<script>
  (async () => {
    const client = await Vallum.createVallumClient({
      endpoint: window.location.origin,
    });

    const response = await client.fetch("/api/protected");
    document.querySelector("#result").textContent =
      JSON.stringify(await response.json(), null, 2);

    window.addEventListener("pagehide", () => client.destroy(), { once: true });
  })().catch((error) => {
    document.querySelector("#result").textContent = error.message;
  });
</script>

The IIFE exposes Vallum.createVallumClient, Vallum.VallumRenderRef, and the same runtime behavior as @liteeagle226/client.

Browser module

<script type="module">
  import { createVallumClient } from
    "https://cdn.jsdelivr.net/npm/@liteeagle226/[email protected]/dist/vallum.esm.js";

  const client = await createVallumClient({ endpoint: location.origin });
  const data = await (await client.fetch("/api/protected")).json();
</script>

The application must already have an authenticated same-origin session, and its backend must expose the Vallum admission route. Loading a script must never grant admission by itself. See @liteeagle226/admission and the client SDK guide.