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

@mlola/browser-runtime

v0.2.10

Published

Public SDK: BrowserAgent over the core runtime with the default Jev + Playwright stack.

Readme

@mlola/browser-runtime

Reliable browser use with a fast path: a local-first browser runtime where browser mechanics, safety, verification and recovery are deterministic, the fast decision path (TypeSafe Jev) handles routine steps, stronger models handle planning and recovery, and a person can take over whenever needed.

npm install @mlola/browser-runtime
import { BrowserAgent } from "@mlola/browser-runtime";

const agent = new BrowserAgent({ decision: { provider: "typesafe" } });

const run = await agent.run({
  goal: "Download my latest invoice, attach it to a new claim, then stop before submitting",
  startUrl: "https://billing.example.com/invoices",
  stopBefore: ["submit claim"],
});

console.log(run.status, run.verification?.status, run.artifacts);
  • Models never produce selectors, coordinates or code — only choices from the runtime's own action space.
  • DONE is a claim; completion is verified by independent evidence (artifacts, URL/state, DOM, runtime events) or a person.
  • Secrets (passwords, OTP, cards) are a takeover floor and never enter model state or traces.

Full documentation: https://mlola.com/browser-runtime