@lit-protocol/contracts 0.1.1

A TypeScript utility for fetching and caching Lit Protocol contract ABIs and addresses. This tool maintains consistent contract data formats across the Lit Protocol ecosystem.

@lit-protocol/contracts@0.1.1 was published on 2025-02-19. Its manifest declares 4 runtime dependencies and 1 peer requirement. 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/contracts versions · Permanent reference to 0.1.1 · View npm registry JSON · Latest release

Package specifications

Version0.1.1
License declarationNot declared
Published2025-02-19T16:54:08.045Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4533.88 KiB
Published file count45
Package typemodule
ES module entry./dist/index.js
Default entry./dist/index.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies27
Repository stars157
Repository forks88

Install @lit-protocol/contracts 0.1.1

npm install @lit-protocol/contracts@0.1.1
pnpm add @lit-protocol/contracts@0.1.1
yarn add @lit-protocol/contracts@0.1.1

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