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

@bugcome/harnessdeck-sdk

v0.1.0

Published

Typed feature detection and Protocol 3 contracts for HarnessDeck plugins

Downloads

151

Readme

@duyanta123/harnessdeck-sdk

Typed, dependency-free feature detection for HarnessDeck Protocol 3. The SDK does not create a privileged channel: it only describes and validates the narrow window.harnessDeck object that Studio injects into pages served by its active loopback Harness.

import { getHarnessDeck, hasHarnessDeckCapability } from '@duyanta123/harnessdeck-sdk'

const desktop = getHarnessDeck(window)
if (desktop) {
  const offer = await desktop.hello()
  if (hasHarnessDeckCapability(offer, 'workspace')) {
    const chosen = await desktop.pick({ mode: 'directory' })
    if (chosen.path) console.log(await desktop.workspace.validate(chosen.path))
  }
}

Use getHarnessDeck() for plugins that also run in an ordinary browser or headless Harness. Use requireHarnessDeck() only when the entire feature is Desktop-specific. Never retain the object across a Harness navigation/restart; feature-detect again in the new page.

The package version follows HarnessDeck while the wire contract has its own integer protocol. A protocol change is intentionally incompatible and must be handled by a new SDK release. See the repository's bilingual plugin contract for the trust boundary and two-phase package policy.

Harness Host plugins

Host plugins can feature-detect the separate, read-only Host Protocol 1. It exposes the active generation's Studio/Harness versions and a bounded Profile roster. It deliberately cannot start commands, access native handles, install packages, or mutate Profiles.

import { getHarnessDeckHost } from '@duyanta123/harnessdeck-sdk'

export const inject = []

export function apply(ctx) {
  const studio = getHarnessDeckHost(ctx)
  if (!studio) return
  ctx.logger.info(
    `running in ${studio.studio.name} ${studio.studio.version} ` +
      `with ${studio.profiles.list().length} profiles`,
  )
}

Use the normal Harness services for agent, model, session, tool, and workspace behavior. Package or Profile changes must continue through Studio's visible, receipt-backed native flows rather than a retained Host reference.