@near-js/crypto 2.3.1

Abstractions around NEAR-compatible elliptical curves and cryptographic keys

@near-js/crypto@2.3.1 was published on 2025-09-10. Its manifest declares 6 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @near-js/crypto versions · Permanent reference to 2.3.1 · Latest release

Package specifications

Version2.3.1
License declarationISC
Published2025-09-10T14:39:38.909Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size41.02 KiB
Published file count31
Package typemodule
ES module entrylib/esm/index.js
Default entrylib/commonjs/index.cjs
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies21
Repository starsUnknown
Repository forksUnknown

Install @near-js/crypto 2.3.1

npm install @near-js/crypto@2.3.1
pnpm add @near-js/crypto@2.3.1
yarn add @near-js/crypto@2.3.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