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

@customyai/data

v0.2.1

Published

Customy Data: typed event tracking (track, identify, page, screen, group, alias) with batching; the scope comes from the credential, never from headers. Over @customyai/core.

Readme

@customyai/data

Eventos tipados hacia Customy Data: track, identify, page, screen, group y alias, directos o en cola con flush por lotes. Sobre @customyai/core. Funciona en servidor, edge y navegador.

npm install @customyai/data @customyai/core
import { createData } from "@customyai/data";
import type { CustomyEventProperties } from "./customy.generated"; // customy apps codegen

// Servidor: la identidad de la app (scope data:collect).
const data = createData<CustomyEventProperties>({ platform, machineTokens });
await data.track("lesson.completed", { lessonId: "l1", minutes: 12 }, { userId: "u1", consent: { analytics: true } });

// Navegador: el write key de la fuente.
const browser = createData<CustomyEventProperties>({ writeKey: "…" });
browser.enqueueTrack("lesson.completed", { lessonId: "l1", minutes: 12 }, { anonymousId });
await browser.flush();
  • Alcance por credencial: organización, proyecto, entorno y fuente salen del write key o del token; un evento con campos de tenant se rechaza (SDK_TENANT_FIELDS_FORBIDDEN). Cabeceras de tenant en headers (x-org-id, x-environment-id…) no se envían: se ignoran con aviso (onWarning, por defecto console.warn).
  • Fuente externa con write key: collectionScope: { sourceId, organizationId, projectId, environmentId, applicationId } viaja en x-customy-collection-*; Data lo compara con la fuente y rechaza con DATA_COLLECTION_SCOPE_MISMATCH si no coincide (nunca concede alcance). Una fuente dedicada a una app externa lo exige. Con un token de Access va firmado en el token y collectionScope se ignora con aviso.
  • verifySource(): GET /v1/collect/source antes de enviar: alcance real de la fuente y gobernanza del contrato.
  • Biblioteca: cada evento lleva context.library = { name: "@customyai/data", version } con la versión del paquete.
  • Entrega: cada evento lleva messageId y Data deduplica, así que los reintentos ante red o 5xx son seguros; un acuse que no confirma cada evento cuenta como fallo y flush devuelve lo no confirmado a la cola, en orden.
  • Privacidad: redactFields y beforeSend.
  • Errores: CustomyDataError (un CustomySdkError con service: "data"); DATA_EVENT_QUARANTINED si el evento quedó en cuarentena.