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

sandcode

v0.0.3

Published

Bun-powered research CLI for OpenCode, Daytona sandboxes, and repository analysis

Downloads

85

Readme

Sandcode

Sandcode is a Bun CLI for ad hoc software research with OpenCode running inside Daytona sandboxes.

It does three things well:

  • sandcode analyze runs evidence-based repository audits from URLs or link files.
  • sandcode start boots an OpenCode web session in a fresh Daytona sandbox.
  • sandcode setup launches an OpenTUI wizard for Obsidian integration and local credentials.

Install

One-off use:

bunx sandcode --help

Global install:

bun add -g sandcode

Bootstrap script:

curl -fsSL https://raw.githubusercontent.com/shpitdev/sandcode/main/scripts/install.sh | bash

Quick Start

First-run setup:

bunx sandcode setup

Analyze a repository:

bunx sandcode https://github.com/octocat/Hello-World

Analyze repositories from a link file:

bunx sandcode links.md

Launch a remote OpenCode web session:

bunx sandcode start

Requirements

  • Bun 1.3+
  • DAYTONA_API_KEY
  • OPENCODE_API_KEY for the built-in opencode-go/* model defaults
  • Optional DAYTONA_API_URL for self-hosted Daytona
  • Optional OPENCODE_SERVER_PASSWORD for sandcode start
  • Optional obsidian CLI for desktop note opening
  • Optional ob CLI for headless Obsidian Sync workflows

Commands

sandcode --help
sandcode analyze --help
sandcode start --help
sandcode setup --help

Examples:

sandcode analyze --input example.md
sandcode analyze --out-dir findings --model opencode-go/kimi-k2.5 https://github.com/owner/repo
sandcode start --port 3000 --target us --keep-sandbox
sandcode setup --yes --vault-path ~/vaults/research --obsidian-integration headless

Setup UX

sandcode setup uses an OpenTUI wizard by default when a TTY is available.

Keyboard controls:

  • Esc goes back one step
  • Ctrl+C exits setup immediately

It writes:

  • ~/.config/sandcode/sandcode.toml
  • ~/.config/sandcode/.env

Project-level overrides are supported with:

  • sandcode.toml
  • .sandcode.toml

Default Obsidian notes root:

[obsidian]
notes_root = "Research/Sandcode"

Headless mode runs a real ob sync-list-remote preflight before it saves.

Repository Audit Workflow

sandcode analyze:

  • creates one Daytona sandbox per target
  • clones the repo inside the sandbox
  • installs OpenCode inside the sandbox
  • runs a headless audit prompt
  • writes findings locally
  • optionally catalogs findings into Obsidian

Default output layout:

  • <out-dir>/index.md
  • <out-dir>/<YYYY-MM-DD-NN-slug>/findings.md
  • <out-dir>/<YYYY-MM-DD-NN-slug>/README.*
  • <out-dir>/<YYYY-MM-DD-NN-slug>/opencode-run.log

If no URLs and no --input are provided, example.md is used when it exists.

Publishing

The package is intended for npm distribution as sandcode.

Release automation, dist-tags, verification, and rollback notes live in RELEASE.md.

Development

bun install
bun run check
bun run typecheck
bun test
bun run build