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

@useatlas/daytona

v0.0.7

Published

Atlas Daytona sandbox plugin

Readme

@useatlas/daytona

Cloud-hosted sandbox isolation via the Daytona SDK.

Install

bun add @useatlas/daytona @daytonaio/sdk

Usage

import { defineConfig } from "@atlas/api/lib/config";
import { daytonaSandboxPlugin } from "@useatlas/daytona";

export default defineConfig({
  plugins: [daytonaSandboxPlugin({ apiKey: process.env.DAYTONA_API_KEY! })],
});

Config

| Field | Type | Default | Description | |-------|------|---------|-------------| | apiKey | string | — | Daytona API key | | apiUrl | string? | cloud endpoint | Daytona API URL override | | timeoutSec | number | 30 | Command timeout in seconds | | target | string? | account default | Daytona region for created sandboxes (e.g. us, eu). Applies to both explore and Python | | pythonPackages | string[] | pandas, numpy, matplotlib, scipy, scikit-learn, statsmodels | Installed once per Python sandbox. Set to [] when your image already bakes them in |

Python execution

This plugin implements the SDK's optional Python surface, so a workspace that selects Daytona runs both explore and executePython on its own Daytona account, in the configured target region. A failure there is an error, not a fallback to the Atlas platform sandbox.

Egress: the host's per-request REST datasource egress bound is applied, so the plugin declares pythonEgressControl: "enforced". Atlas's default for a Python run is deny-all; when a REST datasource is active the bound narrows to that datasource's hosts instead.

The plugin sets it with sandbox.updateNetworkSettings (networkBlockAll for deny-all, domainAllowList for an allowlist) after pythonPackages are installed and before any agent code runs. That ordering is deliberate: Daytona documents its pre-approved essential-services lists (PyPI, npm, GitHub) as no longer applying once a sandbox carries a custom allow list, so narrowing first would break pip install.

⚠️ Two Daytona-side requirements, both of which fail the Python run rather than silently downgrading it to an unbounded sandbox:

  • Per-sandbox network overrides are a Tier 3/Tier 4 organization capability. A Tier 1/2 organization's API rejects the call, and executePython then fails with a named error. Explore is unaffected.
  • @daytonaio/sdk >= 0.201.0, the version this was verified against and the peer range now requires.

Daytona caps a domain allow list at 20 entries; a request carrying more is rejected rather than truncated.

Reference