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

@gscdump/sdk

v3.4.1

Published

Consumer SDK for hosted gscdump.com integrations.

Readme

@gscdump/sdk

Consumer SDK for hosted gscdump.com integrations.

The descriptor-driven HTTP client and ticketed realtime state machine are exported from @gscdump/sdk/v1. Focused helper and compatibility clients use explicit subpaths; the package root is intentionally not importable. The unsafe long-lived-key realtime client was removed before v1. See the integration guide and v1 contract.

This package is for partner applications that consume gscdump.com APIs, webhooks, and realtime events. Callers inject the HTTP transport and auth they want to use; route construction stays inside the hosted adapter. New hosted HTTP integrations should import the stable v1 client:

import { createGscdumpV1Client } from '@gscdump/sdk/v1'

const gscdump = createGscdumpV1Client({
  credential: () => process.env.GSCDUMP_API_KEY!,
  fetch,
})

const lifecycle = await gscdump.getUserLifecycle({
  params: { userId: 'u_01' },
})

The v1 surface uses a server-held Bearer credential and exposes a generic operation executor plus typed convenience methods for all 51 registered HTTP operations across partner, analytics, and realtime.

Focused guides:

createPartnerClient remains at @gscdump/sdk/partner only for operations still in the compatibility inventory. Do not use it for an operation already available from @gscdump/sdk/v1.

Use focused subpaths for pure helpers, including period, period-presets, site-triage, site-baseline, search-console-stage, indexing-issues, analytics, partner, partner-errors, lifecycle, webhook, and gsc-console-url.

For example, a typed hosted report query is:

const report = await gscdump.queryAnalyticsReport({
  params: { siteId: 's_01' },
  body: { state: { dimensions: ['query'], searchType: 'web' } },
})

Scope

  • Partner user lifecycle
  • Partner site lifecycle
  • Data/detail queries
  • Analysis presets
  • Sitemap and indexing reads
  • Webhook receiver contracts and HMAC verification helpers
  • Shared request/response types re-exported from @gscdump/contracts

Analyzer Source dispatch, browser DuckDB-WASM boot, and R2 parquet attach are separate engine/Nuxt concerns. A Nuxt app can consume the hosted SDK through its own query layer; the current consumer uses nuxt-use-query rather than making the public API depend on @gscdump/nuxt.

For v1, a Nuxt consumer keeps user_key and partner_key credentials on its server and exposes proxy paths that retain the upstream surface and major (for example /api/gscdump/analytics/v1/...). Browser realtime receives only a single-use ticket. Every semantic event's changes[] maps to one ordered, awaited query-cache effect; unsafe resync purges the whole host-owned cache scope and primary-reseeds it before the SDK advances its cursor or ACKs.

Boundary

@gscdump/sdk is a consumer SDK. It must not own gscdump.com producer behavior.

Belongs here:

  • request/response types and schemas for partner apps
  • route builders and pluggable HTTP clients
  • ticketed websocket client, replay/resync state, and event schemas
  • awaited realtime apply/resync hooks; a rejected effect never advances ACK
  • webhook header constants, event schemas, parsing, normalization, and signature verification for receivers

Does not belong here:

  • deciding when gscdump.com emits webhooks
  • queueing, retries, backoff, idempotency, or activity logging
  • resolving public user/site IDs from gscdump.com storage
  • generating or storing production webhook secrets
  • creating production webhook delivery IDs or envelopes
  • partner subscription filtering for outgoing deliveries
  • Durable Object stream storage, replay retention, or outbox dispatch

Webhooks

@gscdump/contracts owns the webhook payload schema and event constants. @gscdump/sdk provides receiver-side helpers to parse the payload, verify the signature, and normalize event names. gscdump.com owns webhook production and delivery.

import { parseWebhookPayload } from '@gscdump/sdk/webhook'

const envelope = await parseWebhookPayload(rawJson, {
  secret: webhookSecret,
  signature: request.headers.get('x-gscdump-signature'),
})