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

@harness-fe/core

v4.2.0

Published

Harness-FE core: transport-agnostic capability API + event store + browser-control bridge + identity/canSee/consent. A pure library with no HTTP/WS server — the gateway owns the front door and drives core via the CoreClient interface.

Vulnerabilities

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

Links

Git

Maintainers

pengzai-devpengzai-dev

Keywords

Readme

@harness-fe/core

The transport-agnostic backend of Harness-FE.

core is a pure library — it has no HTTP server, no WebSocket server, and binds no port. It exposes:

  • Capability API — protocol-agnostic functions (args, principal) => result (page.*, *.tail, replay, tasks, project, session, memory). Each enforces canSee tenant isolation, browser consent, and write-scope deny internally, so every front door reuses one authorization model.
  • Bridge — the WS-frame state machine (peer registry, command/response correlation, event persistence) decoupled from the socket implementation via the PeerSocket abstraction. The gateway terminates the runtime WebSocket and feeds the socket in through bridge.acceptPeer(socket, principal).
  • Store / identity / consent — JSONL session store, task store, memory store; the Principal model and canSee / canSeeProject / projectGrant visibility rules.
  • CoreClient — the interface the gateway depends on. The in-process implementation wraps a Bridge directly; a remote (cross-machine) WS variant can implement the same interface without changing the gateway.

The gateway (@harness-fe/gateway) is the only thing that talks to core. Browsers, agents, and humans all reach core through the gateway — never directly.