@metamask/profile-sync-controller 0.0.0

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@0.0.0 was published on 2024-05-09. Its manifest declares 4 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=16.0.0.

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

Package specifications

Version0.0.0
License declarationMIT
Published2024-05-09T15:05:49.491Z
Node.js requirement>=16.0.0
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size268.89 KiB
Published file count151
Package typeNot declared
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies22
Repository stars420
Repository forks312

Install @metamask/profile-sync-controller 0.0.0

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

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.

Evidence and freshness