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

@synapsepkg/marketplace-types

v0.1.0

Published

Synapse marketplace domain model and API contract — shared zod schemas and inferred types for the marketplace server, the plugin CLI, the desktop app, and the web portal

Readme

@synapsepkg/marketplace-types

The Synapse marketplace domain model and HTTP API contract as a single source of truth — shared by the marketplace server, the plugin CLI, the desktop app, and the web portal.

zod schemas are authoritative; TypeScript types are inferred from them (z.infer), so there are no hand-maintained parallel interfaces to drift. A request validated on a client matches exactly what the server parses.

What's here

  • common — shared primitives: pluginId, handle, semver, sha256, timestamp, httpsUrl, localizedString, and the visibility / userRole / pluginStatus / pluginSort enums.
  • domain — entities: User, AuthIdentity, Plugin, PluginVersion, PluginStats, Download, Rating, Review, and the PluginSummary listing projection.
  • api — request/response bodies: device-code auth, search, plugin detail, publish, visibility/yank, download resolution, ratings, reviews, and the uniform apiError envelope.

Conventions

  • Identity is provider-agnostic: a User owns one or more AuthIdentity rows, so adding email/Google later never migrates the user table.
  • Versions are immutable: a bad release is yanked (yankedAt), never deleted, so existing installs stay reproducible.
  • The manifest is the single source of truth for manifestSnapshot: it reuses @synapsepkg/plugin-manifest's manifestSchema, so publish validation and install-time permission disclosure agree with what the plugin host enforces.

Usage

import { searchPluginsQuerySchema, type Plugin } from "@synapsepkg/marketplace-types"

const query = searchPluginsQuerySchema.parse(req.query) // throws on invalid input