Loading…
Loading…
This page names the canonical public package catalog and shows how to install each package. It keeps package names, runtime boundaries, and onboarding language aligned while the broader open-package release surface continues to mature.
Shared types
Use when multiple services or apps need the same GlobiGuard-shaped types and records.
TypeScript/ESM package with no special runtime requirement documented at the package level.
npm install @globiguard/[email protected]pnpm add @globiguard/[email protected]yarn add @globiguard/[email protected]Server and backend integrations
Use for application servers, backend jobs, and deployment paths that need authenticated product access.
Node.js 22+.
npm install @globiguard/[email protected]pnpm add @globiguard/[email protected]yarn add @globiguard/[email protected]React and Next.js apps
Use when the browser app needs GlobiGuard-aware UI helpers or typed React integration.
React 18.3+ or 19.x. Pair @globiguard/react with the browser-safe @globiguard/sdk client.
npm install @globiguard/[email protected]pnpm add @globiguard/[email protected]yarn add @globiguard/[email protected]n8n workflows
Use for n8n-based automation where GlobiGuard participates as a governed-action checkpoint in a workflow node graph.
Node.js 22+ in the n8n environment.
Choose the package based on where your code runs: shared types, backend runtime, React UI, or n8n workflow.
Install it with npm, pnpm, or yarn using the canonical package name shown here.
Configure credentials from the product workspace or your deployment environment, depending on the package and rollout path.
Use the public docs for provider setup and trust context, then request a private review only when your rollout needs customer-specific material.