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

@tangle-network/agent-provider-computesdk

v2.0.1

Published

AgentEnvironmentProvider running CLI Bridge from the box image on any computesdk backing provider

Readme

@tangle-network/agent-provider-computesdk

An AgentEnvironmentProvider whose environments are sandboxes on any computesdk backing provider, each running CLI Bridge from the box image. Turns, profile materialization, refusals, usage and cancellation come from createBridgeSandboxProvider in @tangle-network/agent-provider-cli-bridge/sandbox; this package is the computesdk vendor.

import { compute } from 'computesdk'
import { e2b } from '@computesdk/e2b'
import { createComputeSdkProvider } from '@tangle-network/agent-provider-computesdk'

compute.setConfig({ provider: e2b({ apiKey: process.env.E2B_API_KEY }) })
const provider = createComputeSdkProvider({ compute, router: { key: perRunRouterKey } })

The sandbox boots template (default: the box template pnpm build:sandbox-image --target e2b publishes) with the provider's finite lifetime and the run tag. workspace.environment selects another template or snapshot id. workspace.image boots a box-compatible image (build one with pnpm build:sandbox-image --base-image); a create from any other image fails the Bridge readiness probe. resources and egress are refused, because each backing provider reads them differently — computesdk's egress option is a credential-injection proxy, not the firewall egress means here.

Checkpoints

Pass the computesdk snapshot manager to unlock them: createComputeSdkProvider({ compute: { instances: compute.instances, snapshot: compute.snapshot }, … }) when your backing provider supports snapshots. Every environment then exposes checkpoint() and fork(ref); a fork restores through CreateInstanceOptions.snapshotId, whatever that maps to on the backing provider.

computesdk 4.1 limits what the adapter can prove on every backing provider:

  • getById answers null for any failure, so a transport or auth error reads as an absent sandbox in get and status.
  • list returns no tags, so list reconnects to every sandbox computesdk lists and reads the tags each one carries in TANGLE_BRIDGE_TAGS; the e2b backing provider lists its first page only.
  • destroy swallows failures, so the adapter looks the sandbox up again and throws cleanup_failed while it is still present.

tests/computesdk-live.integration.test.ts runs the live profile conformance suite on the e2b backing provider (E2B_API_KEY) and on the local docker backing provider (CLI_BRIDGE_BOX_IMAGE from pnpm build:sandbox-image --target docker), both with a per-run capped TANGLE_API_KEY.