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

@pipedream/daytona

v0.3.0

Published

Pipedream Daytona Components

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

casretcasretdylburger-workdaydylburger-workdayadolfo-wdadolfo-wdadolfo-pdadolfo-pdalan-pipedreamalan-pipedream

Keywords

pipedreamdaytona

Readme

Overview

Daytona provides secure, elastic sandbox infrastructure for AI agents. Each sandbox is a complete, isolated environment that is fully programmable, spun up on demand, and built for autonomous use without human intervention.

Using Pipedream, you can integrate Daytona into any automated workflow: create sandboxes from snapshots or custom images, clone repositories, execute code and shell commands, expose running services via preview URLs, and manage the full sandbox lifecycle — all as composable steps alongside thousands of other apps.

Example Use Cases

  • AI Code Execution Pipeline: Trigger a workflow when a new message arrives in Slack, send the message to an AI model (e.g., OpenAI) to generate code, then execute that code safely in a Daytona sandbox using the Run Code action and return the results back to Slack.

  • Automated Testing in Isolated Environments: When a pull request is opened on GitHub, create a Daytona sandbox, Clone the Git Repository into it, run the test suite with Run Command, and post the results as a PR comment, all without touching your local infrastructure.

  • On-Demand Dev Environments: Use a webhook or form trigger to spin up a Daytona sandbox, clone a repo, run setup commands via Run Command (e.g., npm install), start a dev server, and share the Preview Link with your team for review.

Getting Started

Authentication

Daytona uses API key-based authentication. To connect your Daytona account:

  1. Go to app.daytona.io/dashboard/keys
  2. Click Create Key and generate a new API key
  3. In Pipedream, add a new Daytona connection and paste your API key

Available Actions

| Action | Description | |---|---| | Clone Git Repository | Clone a public or private Git repository into a sandbox | | Create Sandbox | Create a new isolated sandbox with configurable language, resources, and lifecycle settings | | Delete Sandbox | Permanently delete a sandbox and all its data | | Get Sandbox | Retrieve details about a specific sandbox | | Get Preview Link | Get a preview URL for a service running on a specific port in a sandbox | | List Sandboxes | List sandboxes with optional label filtering and pagination | | List Snapshots | List available sandbox snapshots (pre-configured templates) | | Start Sandbox | Start a stopped sandbox | | Stop Sandbox | Stop a running sandbox | | Run Command | Execute a shell command inside a sandbox | | Run Code | Execute Python, TypeScript, or JavaScript code inside a sandbox | | Create SSH Access | Generate a time-limited SSH access token for a sandbox | | Revoke SSH Access | Revoke an SSH access token | | Wait Until Stopped | Wait for a sandbox to reach the stopped state |

Links

Troubleshooting

Toolbox actions fail with a validation error

Actions that interact with a running sandbox (Run Code, Run Command, Clone Git Repository, Get Preview Link) require the sandbox to be in a started state. If your sandbox has auto-stopped due to inactivity, add a Start Sandbox step before these actions in your workflow.

Clone Git Repository returns a 400 error

The destination path likely already exists in the sandbox from a previous run. Use a unique path for each execution, or add a Run Command step before the clone to remove the existing directory:

rm -rf /path/to/destination

Private repository clone fails with authentication error

Ensure you are passing your Git username (not email) and a valid personal access token (PAT) with repository read access in the Password / Token field — not your account password.

GitHub fine-grained tokens may not work reliably with git operations over HTTPS. If cloning fails, use a classic token instead: go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic) and generate one with the repo scope.

API key errors

Verify your API key is valid and has not expired at app.daytona.io/dashboard/keys. API keys can be scoped — ensure the key has permissions for the operations you are performing (e.g., write:sandboxes to create sandboxes).