@metamask/profile-sync-controller 34.0.2

The profile sync helps developers synchronize data across multiple clients and devices in a privacy-preserving way. All data saved in the user storage database is encrypted client-side to preserve privacy. The user storage provides a modular design, givin

@metamask/profile-sync-controller@34.0.2 was published on 2026-10-08. Its manifest declares 15 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^22.14.0 || ^24.

All @metamask/profile-sync-controller versions · Permanent reference to 34.0.2 · Latest release

Package specifications

Version34.0.2
License declarationMIT
Published2026-10-08T19:08:15.990Z
Node.js requirement^22.14.0 || ^24
Type declarationsBundled declarations
Runtime dependency count15
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size994.13 KiB
Published file count241
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies261
Repository stars420
Repository forks312

Install @metamask/profile-sync-controller 34.0.2

npm install @metamask/profile-sync-controller@34.0.2
pnpm add @metamask/profile-sync-controller@34.0.2
yarn add @metamask/profile-sync-controller@34.0.2

Runtime dependencies

Peer requirements

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.

Evidence and freshness