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

@glasshome/widget-contract

v0.2.1

Published

Shared widget contract for GlassHome: manifest schema, capability grammar and enforcement predicate, bundle paths, SDK version compatibility

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ihsenihsen

Keywords

glasshomewidgetscapabilitiesmanifestsmart-home

Readme

@glasshome/widget-contract

The shared contract between every part of the GlassHome widget pipeline: the widget SDK (author declarations), the Hub (publish validation), and Dash (install consent and runtime enforcement).

The capability set shown at consent, validated at publish, and enforced at the HA bridge must be computed by the same code. If they drift, the consent screen lies, and that is a vulnerability. This package is that single definition.

Exports

  • capabilitiesSchema / capabilityGrantSchema — the capability grammar widgets declare in their manifest. One grant = one consent sentence: a Home Assistant domain, read or control access, optional entity-pattern and service narrowing.
  • matchesCapability(caps, rpc) — the pure enforcement predicate. The Dash HA bridge validates every widget service call with it; deny by default.
  • describeCapability(cap) — renders a grant as the plain-language consent sentence ("Control your lights"). Same object enforcement uses, so consent cannot drift from enforcement.
  • widgetManifestSchema / publishManifestSchema — the canonical widget manifest schema; the publish variant requires a capabilities declaration for SDK >= 1.0.0 manifests.
  • bundleKey(scope, name, version, file) — canonical storage path for published widget files (index.js / index.css).
  • checkSdkCompat / satisfiesSdk / requiresCapabilities — SDK version compatibility rules shared by loader, installer, and Hub search.

Design notes

  • Zero UI dependencies. Runs in Node (Hub), the browser main thread (consent UI), and a Web Worker (enforcement).
  • matchesCapability requires entity ids; target expansion (area/device/label to entities) happens in the caller before the check.
  • Entity narrowing patterns keep the domain literal (light.living_*), so a pattern can never widen a grant beyond its domain.

Part of the GlassHome widget security architecture.