New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started
b

bobsingor

npm

28.88M

total weekly downloads

Packages

Current Co-maintainers

Former Co-maintainers

123 packages

@cloudpdf/admin

CloudPDF admin SDK. Node-only client used by a customer's backend to upload PDFs, manage documents, and mint user tokens against a @cloudpdf/server deployment.

@cloudpdf/admin-api

Shared CloudPDF admin HTTP contracts and zod schemas, used by both @cloudpdf/server and the @cloudpdf/admin SDK.

@cloudpdf/api

CloudPDF API Wrapper

@cloudpdf/contract

The CloudPDF engine contract: operation registry, Zod schemas, and OpenAPI emitter for every backend-callable surface — used by @cloudpdf/server and the generated @cloudpdf/sdk, and the source of the committed openapi.json.

@cloudpdf/engine

CloudPDF engine: the cloud client that speaks the Engine v3 interface over HTTPS to a @cloudpdf/server deployment (or CloudPDF SaaS). Same AbortablePromise-based, EngineError-coded contract as the local engine.

@cloudpdf/plugin-protected-display

Screenshot protection for the CloudPDF viewer: for a user who may read a document but not render its pages, it shows them as DRM-protected video frames from the protected display server module, so screenshots, recordings and shared screens show them black

@cloudpdf/sdk

The official TypeScript SDK for the CloudPDF API.

@cloudpdf/server

Self-hostable CloudPDF document engine server: Fastify-based HTTP/REST API in front of a Node worker_thread pool running the native EmbedPDF Runtime (PDFium fork) via @embedpdf/engine-runtime. Uses the same engine-services code as the local browser engine

@cloudpdf/server-modules

Write CloudPDF server modules: packages that run inside @cloudpdf/server with their own routes and permissions, and reach documents through the engine's document API, as the caller and as themselves.

@cloudpdf/viewer

A complete PDF viewer for any web page, with CloudPDF as its engine: the file stays on the server, and pages arrive as images.

@cloudpdf/viewer-angular

A complete PDF viewer as an Angular component, with CloudPDF as its engine: the file stays on the server, and pages arrive as images.

@cloudpdf/viewer-react

A complete PDF viewer as a React component, with CloudPDF as its engine: the file stays on the server, and pages arrive as images.

@cloudpdf/viewer-svelte

A complete PDF viewer as a Svelte component, with CloudPDF as its engine: the file stays on the server, and pages arrive as images.

@cloudpdf/viewer-vue

A complete PDF viewer as a Vue component, with CloudPDF as its engine: the file stays on the server, and pages arrive as images.

@cloudpdf/web

Framework-free browser code for CloudPDF's plugins: the one home in the CloudPDF tree for code that touches the DOM, as @embedpdf/web is for EmbedPDF's. Today the protected display player: Encrypted Media Extensions and Media Source behind @cloudpdf/plugi

creditguard-api

Simple wrapper for Creditguard API

easybotflow

@embedpdf/ai

AI runtime for EmbedPDF – manages ONNX model loading, inference, and built-in pipelines (layout detection, table structure) across browser and Node.js.

@embedpdf/angular

Angular services and components for building your own PDF viewer with EmbedPDF.

@embedpdf/core

The kernel of EmbedPDF's headless viewer: plugins, what each one can do, and their state. No DOM, no framework.

@embedpdf/core-acrojs

The Acrobat JavaScript a PDF's scripts expect, for EmbedPDF: its objects, its security rules and the code a sandbox starts with.

@embedpdf/core-annotation

The pure annotation brain: model · update(msg)→[model,effects] · view. Content-space geometry per family, hit-testing, and tools. No DOM, engine, or framework dependencies.

@embedpdf/core-fonts

The 14 standard PDF fonts as the EmbedPDF engine draws them: font files a browser can load, and the measures the engine lays text out with.

@embedpdf/core-form

Draws PDF form fields for EmbedPDF as the engine draws them. No DOM.

@embedpdf/core-geometry

Points, sizes, boxes and page rotation for EmbedPDF, with the transforms between a page, the view and the screen. No dependencies, no DOM.