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

@contract-case/case-connector

v0.30.0

Published

Connector to allow ContractCase to run as a server. Use only if you're creating a custom wrapper for a new language

Vulnerabilities

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

Links

Git

Maintainers

timothyjonestimothyjones

Keywords

Readme

Case-Connector

Build and test Known Vulnerabilities

This is the server connector (formerly case-boundary) to allow ContractCase to be run as a server.

If you're wanting to learn about ContractCase, start here instead

Don't depend on this directly unless you are writing a custom wrapper for ContractCase.

This package exists to work around this JSii bug, by exposing the communication layer as a gRPC service.

Additionally, it exposes the boundary layer as @contract-case/case-connector for ESM imports, and @contract-case/case-connector/cjs for CJS imports.

For details of the protocol schema, see the case-connector-proto package.

Authentication

The connector binds to the loopback interface only, on a free port that it announces on stdout in the form:

[SERVER] Started on port: <PORT>

To prevent other local processes from connecting to it, wrappers must generate an unguessable random token and pass it to the connector process via the CASE_CONNECTOR_TOKEN environment variable. The connector rejects (with UNAUTHENTICATED) any call that doesn't present the same token in the authorization metadata of the gRPC call.

If CASE_CONNECTOR_TOKEN is not set, the connector refuses to start. This means the connector always requires a compatible wrapper (any wrapper released after the token was introduced).