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

@sorqen/resolver

v0.1.0

Published

Resolve supported Polymarket and Kalshi identifiers to canonical Sorqen sports IDs locally, offline and without venue credentials.

Readme

@sorqen/resolver

Resolve supported prediction-market identifiers into canonical Sorqen sports IDs locally.

No Sorqen API key, venue credential, account or network call is required for the resolver itself.

npm i @sorqen/resolver
import { kalshi } from '@sorqen/resolver';

const resolved = kalshi.resolveKalshi({
  league: 'nfl',
  eventTicker: 'KXNFLGAME-26SEP21NYGLAR',
  knownAbbrevs: new Set(['NYG', 'LAR']),
  marketType: 'moneyline',
  selection: 'LAR'
});

The result contains canonical Sorqen event/market/outcome identity when the ticker can be resolved unambiguously. Ambiguous or unparseable input returns no asserted match rather than guessing.

Where it fits

Sorqen's hosted API provides authenticated sportsbook-derived fair value. Prediction-market prices remain with the caller. The normal local workflow is:

  1. Fetch Sorqen fair value using a Free or paid Sorqen key.
  2. Fetch venue data using your own lawful venue access.
  3. Resolve the venue ticker locally with @sorqen/resolver.
  4. Compare locally with @sorqen/client.

The resolver does not contain Sorqen fair-value data and cannot bypass Sorqen authentication or plan entitlements.

Why resolution is strict

Venue identifiers can encode compact team blocks, local dates, start times and doubleheader ordinals. Different sources also use different abbreviations for the same club. A wrong canonical match is more dangerous than an unmatched market, so the resolver refuses ambiguous inputs instead of choosing the most convenient-looking split.

Package boundary

@sorqen/resolver is MIT-licensed local code. It canonicalizes identifiers; it is not a Polymarket/Kalshi proxy and does not redistribute venue data.

Part of Sorqen.