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

@veris-ai/e2b

v0.1.1

Published

Veris dependency-sandbox interception for E2B: a drop-in Sandbox subclass whose vendor API calls are answered by stateful Veris twins. Unmodified code, real hostnames, receipts.

Readme

Veris SDK for E2B

Run your code in an E2B sandbox where calls to api.stripe.com, www.googleapis.com, and the rest of your vendor stack are answered by Veris dependency sandboxes — stateful, contract-accurate mocks — with the code under test completely unmodified.

No base-URL overrides, no injected config. Your code keeps its production hostnames, credentials, and SDKs; the network layer does the rest.

1. Install

npm i @veris-ai/e2b

This package re-exports everything from e2b, so it's the only one you need.

2. Get your keys

| Variable | Where from | |---|---| | E2B_API_KEY | e2b.dev/dashboard | | VERIS_API_KEY | your Veris dashboard | | VERIS_ENVIRONMENT_ID | a Veris environment — it decides which vendor services your sandbox gets |

export E2B_API_KEY=e2b_…
export VERIS_API_KEY=…
export VERIS_ENVIRONMENT_ID=…

3. Run code against mocked vendors

import { Sandbox } from '@veris-ai/e2b'

const sbx = await Sandbox.create()

// api.stripe.com is answered by your Veris mock — the code never knows.
const res = await sbx.commands.run(
  'curl -sS https://api.stripe.com/v1/customers -u sk_test_veris:'
)
console.log(res.stdout)

await sbx.kill()

4. Check the receipt

A test suite that quietly stopped calling its dependency prints the same output as one that works. The receipt is how you tell them apart:

// throws unless the service actually saw a matching request
await sbx.veris.assertTouched('stripe', { method: 'POST', path: '/v1/charges' })

Verify it end to end

examples/verify.mjs stands up a sandbox, reads the credentials the mocks publish, makes authenticated calls to www.googleapis.com and api.stripe.com, and asserts from the receipt that the mocks served them:

node examples/verify.mjs

5. Check out the docs

Development

npm install
npm run build      # tsup (ESM+CJS) + tsc (declarations)
npm test           # unit tests — mocked, no account needed
npm run typecheck

Live tests need real credentials and are opt-in:

VERIS_E2E=proxy npm run test:live

License

Apache-2.0