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

@vibedgc/sdk

v0.6.10

Published

Embed the DGC coding harness in applications and CI

Readme

@vibedgc/sdk

Node client for the DGC coding harness. It starts a managed dgc serve child with an isolated HOME and speaks editor protocol v14. Version 0.6.10 pairs with DGC CLI 0.47.0. Node 22 or newer.

The package is on the npm registry. The identical tarball is also attached to the GitHub release sdk-v0.6.10 as vibedgc-sdk-0.6.10.tgz, for installs that pin a checksum.

npm install @vibedgc/sdk
import { mkdtempSync } from "node:fs";
import { tmpdir } from "node:os";
import { join } from "node:path";
import { DGC } from "@vibedgc/sdk";

const dgc = new DGC({
  stateDir: mkdtempSync(join(tmpdir(), "dgc-sdk-")),
  model: process.env.DGC_MODEL,          // for example "qwen3:8b"
  baseUrl: process.env.DGC_BASE_URL,     // for example "http://127.0.0.1:11434/v1"
});
try {
  const session = await dgc.session({
    cwd: process.cwd(),
    permissions: { mode: "plan", unhandled: "deny" },
  });
  const result = await session.run("Summarize this repository in two sentences.");
  console.log(result.status, result.finalText);
} finally {
  await dgc.close();
}

The SDK needs a DGC CLI (0.47.0 or newer). It uses DGC_PYTHON when set, else the installed dgc launcher (on PATH or ~/.local/bin/dgc, where curl -fsSL https://vibedgc.com/install.sh | bash puts it), else python3 -m dgc. Pass runtime: [...] to choose explicitly.

Each session runs with a private, freshly written config: nothing left in stateDir is merged, the workspace cannot grant itself capabilities (trustWorkspace: true opts in), the provider key never enters the runtime's environment, and a policy (tool, path, network and shell limits) is enforced by the runtime for that session only, in every permission mode. Every error is a DGCError subclass (DGCConfigError, DGCRuntimeError, DGCProtocolError, DGCCommandRejectedError, DGCTimeoutError, DGCUnsupportedError). Times are milliseconds: run(prompt, { timeoutMs: null }) has no limit, and { signal } takes an AbortSignal that cancels the run.

The runtime child sees only basic variables (PATH, locale, terminal, temp and certificate locations), the isolated HOME, apiKey and extraEnv. Pass inheritEnv: ["NAME"] (or true) to hand it more of your environment.

Full reference: docs/SDK.md. Licensed under Apache-2.0.