@uppy/companion-client 2.2.2

Client library for communication with Companion. Intended for use in Uppy plugins.

@uppy/companion-client@2.2.2 was published on 2022-08-17. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @uppy/companion-client versions · Permanent reference to 2.2.2 · Latest release

Package specifications

Version2.2.2
License declarationMIT
Published2022-08-17T17:51:57.301Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size71.88 KiB
Published file count30
Package typemodule
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies3
Repository stars31048
Repository forks2112

Install @uppy/companion-client 2.2.2

npm install @uppy/companion-client@2.2.2
pnpm add @uppy/companion-client@2.2.2
yarn add @uppy/companion-client@2.2.2

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Code-Review10/10 — all changesets reviewed
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Packaging10/10 — packaging workflow detected

Evidence and freshness