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

@amond-ai/harness-sandbox

v0.2.0

Published

The AI SDK harness's HarnessV1SandboxProvider, written once over @amond-ai/sandbox so every backend behind that contract gets one

Readme

@amond-ai/harness-sandbox

The AI SDK harness's HarnessV1SandboxProvider, written once over @amond-ai/sandbox — so every backend behind that contract gets one, with no harness-shaped code in any of them.

import { createHarnessSandboxProvider } from '@amond-ai/harness-sandbox'
import { createE2bProvider, e2bSandboxApi } from '@amond-ai/sandbox-e2b'

const harnessSandbox = createHarnessSandboxProvider({
  sandboxes: createE2bProvider({ api: e2bSandboxApi({ apiKey: process.env.E2B_API_KEY }) }),
  defaultWorkingDirectory: '/workspace',
  ports: [30_000],
})

providerId defaults to pleaseai-<backend>, so a diagnostic names the backend that produced it. newSessionId is injected only so a test can pin the minted id.

The translation, and where it stops

The contract is declared in Cloudflare's shape rather than the harness's, because that is the shape a backend can satisfy with no mapping. The harness's own shape is a further translation — and this package is where it lives, so the dozen modules of a backend never see it.

Four surfaces make up the provider, and each is exported on its own for a backend that needs only part of it:

| Export | What it translates | | --- | --- | | createHarnessSandboxProvider | SandboxProvider → HarnessV1SandboxProvider | | createHarnessSandboxSession | SandboxSession → the harness's session | | createProcessSurface | SandboxProcessHandle → the harness's process, including splitProcessStreams | | createFileSurface | The contract's file calls → the harness's file surface |

identity — the framework's key for snapshot-based reuse — is ignored, because the contract has no snapshot primitive to key anything on. A backend that grows one answers it there, through the sandbox id it is already addressed by.

License

Apache-2.0 — see LICENSE.