
Security News
gem.coop Tests Dependency Cooldowns as Package Ecosystems Move to Slow Down Attacks
gem.coop is testing registry-level dependency cooldowns to limit exposure during the brief window when malicious gems are most likely to spread.
@durable-streams/cli
Advanced tools
A command-line tool for interacting with durable streams.
# Global installation
npm install -g @durable-streams/cli
# Or run directly with npx
npx @durable-streams/cli create my-stream
npx @durable-streams/cli read my-stream
# Clone the repository
git clone https://github.com/durable-streams/durable-streams.git
cd durable-streams
# Install dependencies
pnpm install
# Build the CLI
pnpm build
# Link globally for development (uses tsx, no rebuild needed)
cd packages/cli
pnpm link:dev
# Now you can use durable-stream-dev anywhere
durable-stream-dev create my-stream
The easiest way to get started is to run the local development server and use the CLI:
pnpm start:dev
This will start a Durable Streams server at http://localhost:4437 with live reloading.
# Set the server URL (optional, defaults to http://localhost:4437)
export STREAM_URL=http://localhost:4437
# Create a stream
durable-stream-dev create my-stream
# Write to the stream
durable-stream-dev write my-stream "Hello, world!"
# Read from the stream (follows live)
durable-stream-dev read my-stream
STREAM_URL - Base URL of the stream server (default: http://localhost:4437)STREAM_AUTH - Authorization header value (e.g., Bearer my-token)--auth <value> - Authorization header value (overrides STREAM_AUTH env var)--content-type <type> - Content-Type for the message (default: application/octet-stream)--json - Shorthand for --content-type application/jsondurable-stream-dev create <stream_id>
# Write content as arguments
durable-stream-dev write <stream_id> "Hello, world!"
# Pipe content from stdin
echo "Hello from stdin" | durable-stream-dev write <stream_id>
cat file.txt | durable-stream-dev write <stream_id>
# Specify content type
durable-stream-dev write <stream_id> '{"key": "value"}' --content-type application/json
# Shorthand for JSON
durable-stream-dev write <stream_id> '{"key": "value"}' --json
In JSON mode (--json or --content-type application/json), top-level arrays are flattened into individual messages:
| Input | Messages stored |
|---|---|
{} | 1 message: {} |
[{}, {}] | 2 messages: {}, {} |
[[{}, {}]] | 1 message: [{}, {}] |
This matches the protocol's batch semantics.
# Follows the stream and outputs new data to stdout
durable-stream-dev read <stream_id>
durable-stream-dev delete <stream_id>
Use the --auth flag or STREAM_AUTH environment variable to authenticate:
# Using environment variable
export STREAM_AUTH="Bearer my-token"
durable-stream-dev read my-stream
# Using --auth flag (overrides env var)
durable-stream-dev --auth "Bearer my-token" read my-stream
# Works with any auth scheme
durable-stream-dev --auth "Basic dXNlcjpwYXNz" read my-stream
durable-stream-dev --auth "ApiKey abc123" read my-stream
# Terminal 1: Start the local development server
pnpm start:dev
# Terminal 2: Set up the stream
export STREAM_URL=http://localhost:4437
durable-stream-dev create test-stream
# Terminal 3: Start reading (will show data as it arrives)
export STREAM_URL=http://localhost:4437
durable-stream-dev read test-stream
# Back in Terminal 2: Write data and watch it appear in Terminal 3
durable-stream-dev write test-stream "First message"
durable-stream-dev write test-stream "Second message"
echo "Piped content!" | durable-stream-dev write test-stream
# Start the example server with live reloading
pnpm start:dev
# Watch mode for CLI development (rebuilds dist/)
pnpm dev
# Build
pnpm build
# Link globally for development (uses tsx, no rebuild needed)
pnpm link:dev
FAQs
CLI tool for working with Durable Streams
We found that @durable-streams/cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
gem.coop is testing registry-level dependency cooldowns to limit exposure during the brief window when malicious gems are most likely to spread.

Security News
Following multiple malicious extension incidents, Open VSX outlines new safeguards designed to catch risky uploads earlier.

Research
/Security News
Threat actors compromised four oorzc Open VSX extensions with more than 22,000 downloads, pushing malicious versions that install a staged loader, evade Russian-locale systems, pull C2 from Solana memos, and steal macOS credentials and wallets.