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

@vladchatware/tool-docker

v0.1.0-rc.5

Published

Docker bash tool for DeepSeek Harness

Readme

@vladchatware/dsh-tool-docker

Model-facing docker_bash tool: run untrusted code inside the isolated Docker container owned by @vladchatware/dsh-docker, alongside the host execution world. Mount both this tool and the owner in a composition to give the agent container execution without replacing the host bash/fs tools.

- id: docker
  name: '@vladchatware/dsh-docker'
  config:
    image: debian:bookworm-slim
    cwd: /workspace
    timeoutMs: 180000
    volume: dsh-web-workspace
    lazy: true

- id: tool-docker
  name: '@vladchatware/dsh-tool-docker'

lazy: true boots the container only on the first docker_bash call, so a session that never touches the container costs nothing.

Configuration

| Key | Default | Meaning | |---|---|---| | maxOutputBytes | 65536 | Per-stream output cap; overflow keeps the tail and sets truncated | | timeoutMsCap | 60000 | Cap on the tool's timeoutMs parameter (silently clamped) |

Model Experience

docker_bash tool schema

What the model sees

A single tool, docker_bash, that runs one bash command inside the isolated Docker container — a separate machine from the host with its own filesystem at /workspace backed by a persistent volume. Parameters: command (required), description (required), workdir (default: the owner's cwd, /workspace), and timeoutMs (clamped to the cap). It returns exitCode, stdout, stderr, truncated, and timedOut; a timeout kills the whole process group. Registered alongside the host bash tool — use docker_bash for untrusted code, experiments, or anything that must not touch the host. See the tool catalog.

Token effect

Each docker_bash call contributes the command, description, and returned stdout/stderr bounded to maxOutputBytes per stream; an internal list delimiter separates stderr. A truncated or timed-out tail is marked explicitly.

KV Cache effect

No direct invalidation; the rendered result is a fresh call each time, so the request prefix is unchanged.

Known Limitations and Deferred Work

  • Container output is bounded but not spilled — overflow keeps the tail with a truncated marker; no host spill file for full retention (unlike the subprocess adapter's collect mode).
  • Runs as root by default — dropping to a non-root user in the tool target is a follow-up.