@near-js/crypto 0.0.1
Abstractions around NEAR-compatible elliptical curves and cryptographic keys
@near-js/crypto@0.0.1 was published on 2023-03-30. Its manifest declares 4 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.
All @near-js/crypto versions · Permanent reference to 0.0.1 · Latest release
Package specifications
| Version | 0.0.1 |
|---|---|
| License declaration | ISC |
| Published | 2023-03-30T20:50:17.637Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 19.67 KiB |
| Published file count | 27 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @near-js/crypto 0.0.1
npm install @near-js/crypto@0.0.1 pnpm add @near-js/crypto@0.0.1 yarn add @near-js/crypto@0.0.1
Runtime dependencies
- bn.js 5.2.1
- borsh ^0.7.0
- tweetnacl ^1.0.1
- @near-js/types 0.0.1
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.
- @near-js/types@0.0.1 — direct
- base-x@3.0.11 — indirect
- bn.js@5.2.1 — direct
- borsh@0.7.0 — direct
- bs58@4.0.1 — indirect
- safe-buffer@5.2.1 — indirect
- text-encoding-utf-8@1.0.2 — indirect
- tweetnacl@1.0.3 — direct
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
- https://registry.npmjs.org/%40near-js%2Fcrypto/0.0.1 — retrieved 2026-10-30T06:56:09.500Z
- https://api.deps.dev/v3/systems/npm/packages/%40near-js%2Fcrypto/versions/0.0.1 — retrieved 2026-10-30T06:56:10.088Z
- https://api.deps.dev/v3/systems/npm/packages/%40near-js%2Fcrypto/versions/0.0.1:dependencies — retrieved 2026-10-30T06:56:10.113Z