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

@qadi/promise

v0.4.0

Published

A Promise-returning facade over @qadi/core, for callers who do not use Effect

Readme

@qadi/promise

A Promise-returning facade over @qadi/core, for callers who do not use Effect.

pnpm add @qadi/promise @qadi/core effect

One rule, and it is the whole package

No branch in it decides anything. Every method forwards to the core evaluator. A facade that only forwards cannot drift from the thing it wraps; one that decides can, and the predecessor's second evaluation path destroyed short-circuiting and left an entire API unreachable.

const qadi = makeQadi(runtime);

if (await qadi.check(subject, policy)) {
  // ...
}

A denial resolves; a failure rejects

try { check() } catch { return false } is the natural Promise idiom and turns an attribute-store outage into a silent lockout. So a denial is a resolved false, and only a broken dependency rejects.

assert is the deliberate exception: there the caller has said "proceed only if permitted", so a denial rejects too.

The subject travels per call rather than living in the layer, so one runtime serves every user.

License

MIT