@lit-protocol/sev-snp-utils-sdk 6.0.0-beta.testing2

Read more about it here

@lit-protocol/sev-snp-utils-sdk@6.0.0-beta.testing2 was published on 2024-05-20. 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.

Deprecated: This package targets a retired Lit Protocol network and is no longer maintained. See https://developer.litprotocol.com for the current SDK.

All @lit-protocol/sev-snp-utils-sdk versions · Permanent reference to 6.0.0-beta.testing2 · View npm registry JSON · Latest release

Package specifications

Version6.0.0-beta.testing2
License declarationMIT
Published2024-05-20T23:08:52.359Z
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 size360.60 KiB
Published file count8
Package typecommonjs
ES module entryNot declared
Default entry./src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies3
Repository stars157
Repository forks88

Install @lit-protocol/sev-snp-utils-sdk 6.0.0-beta.testing2

npm install @lit-protocol/sev-snp-utils-sdk@6.0.0-beta.testing2
pnpm add @lit-protocol/sev-snp-utils-sdk@6.0.0-beta.testing2
yarn add @lit-protocol/sev-snp-utils-sdk@6.0.0-beta.testing2

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