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

@gyoungwe/plugin-api

v1.2.0

Published

Stable host contracts for Drone capability plugins

Readme

@gyoungwe/plugin-api

Stable, host-independent TypeScript contracts for Drone capability plugins. The package contains no Electron, backend, Pi SDK, filesystem, or network implementation. A host implements DroneHostPort and performs the capability negotiation before loading a plugin. Analysis-capable plugins additionally expose the versioned AnalysisHostPort registry through their host entry; the host consumes that loader without importing adapter implementations.

The package is intentionally published at API major 1 while its npm scope is still a project decision. Before publication, the host and drone-plugins workspace use an npm pack tarball or a pinned git commit; they must never use a relative path into the Drone source repository.

compatible and incompatible are the only negotiation outcomes in API v1. There is no implicit partial or degraded load: a plugin that cannot satisfy its declared requirements is refused with an actionable reason.

Hosts that execute an L1 plugin should wrap the port they pass to it with createPermissionedHostPort. The wrapper treats the manifest's filesystem, network, subprocess and externalWrites declarations as a deny gate before calling the host authorization UI, and emits redacted PluginPermissionAuditEvent records for denied and decided operations. This is the executable permission contract for host-mediated side effects; it does not claim to sandbox direct Node.js access from an untrusted plugin. Hosts may additionally load optional extensions through Drone's process sandbox proxy; that runtime boundary is a host capability and must not be implied by a manifest declaration.

The candidate package is 1.2.0; the current public release remains 1.1.0. API v1 is additive-only: publish a new minor or patch only when the contract changes, verify the packed tarball in a clean consumer before release, and never overwrite an existing version.

Desktop knowledge UI contract

@gyoungwe/plugin-api/ui exports the type-only KnowledgeUiPort, KnowledgeUiBindings, DroneUiRuntime, and KnowledgeSurfaceProps contracts. A UI plugin accesses services through window.DroneUI.knowledge; the host retains authorization, Vault boundaries, and persistence. The port is an explicit list of 56 required methods, not the complete preload API. React bindings require React 19 types only when importing this UI subpath; the package has no runtime dependency.

src/ui-wire.ts is generated from the shared wire contracts and existing public knowledge types. The allowlist in scripts/knowledge-ui-contract.json fixes the public scope. In the source checkout, run node scripts/generate-knowledge-ui-contract.mjs after changing a wire type. Package build and typecheck reject a stale generated contract.