near-api-js 5.1.0
JavaScript library to interact with NEAR Protocol via RPC API
near-api-js@5.1.0 was published on 2025-03-05. Its manifest declares 17 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-api-js versions · Permanent reference to 5.1.0 · View npm registry JSON · Latest release
Package specifications
| Version | 5.1.0 |
|---|---|
| License declaration | (MIT AND Apache-2.0) |
| Published | 2025-03-05T20:15:28.962Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 17 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 47.13 KiB |
| Published file count | 71 |
| 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 | 52 |
| Repository stars | 429 |
| Repository forks | 267 |
Install near-api-js 5.1.0
npm install near-api-js@5.1.0 pnpm add near-api-js@5.1.0 yarn add near-api-js@5.1.0
Runtime dependencies
- depd 2.0.0
- borsh 1.0.0
- near-abi 0.2.0
- node-fetch 2.6.7
- http-errors 1.7.2
- @noble/curves 1.8.1
- @near-js/types 0.3.1
- @near-js/utils 1.1.0
- @near-js/crypto 1.4.2
- @near-js/signers 0.2.2
- @near-js/accounts 1.4.0
- @near-js/keystores 0.2.2
- @near-js/providers 1.0.2
- @near-js/transactions 1.3.2
- @near-js/keystores-node 0.1.2
- @near-js/wallet-account 1.3.2
- @near-js/keystores-browser 0.2.2
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/accounts@1.4.0 — direct
- @near-js/crypto@1.4.2 — direct
- @near-js/keystores@0.2.2 — direct
- @near-js/keystores-browser@0.2.2 — direct
- @near-js/keystores-node@0.1.2 — direct
- @near-js/providers@1.0.2 — direct
- @near-js/signers@0.2.2 — direct
- @near-js/transactions@1.3.2 — direct
- @near-js/types@0.3.1 — direct
- @near-js/utils@1.1.0 — direct
- @near-js/wallet-account@1.3.2 — direct
- @noble/curves@1.8.1 — direct
- @noble/hashes@1.3.3 — indirect
- @noble/hashes@1.7.1 — indirect
- @scure/base@1.2.6 — indirect
- @types/json-schema@7.0.15 — indirect
- bn.js@4.12.5 — indirect
- borsh@1.0.0 — direct
- brorand@1.1.0 — indirect
- depd@1.1.2 — indirect
- depd@2.0.0 — direct
- elliptic@6.6.1 — indirect
- exponential-backoff@3.1.3 — indirect
- generate-function@2.3.1 — indirect
- generate-object-property@1.2.0 — indirect
- hash.js@1.1.7 — indirect
- hmac-drbg@1.0.1 — indirect
- http-errors@1.7.2 — direct
- inherits@2.0.3 — indirect
- inherits@2.0.4 — indirect
- is-my-ip-valid@1.0.1 — indirect
- is-my-json-valid@2.20.6 — indirect
- is-property@1.0.2 — indirect
- jsonpointer@5.0.1 — indirect
- lru_map@0.4.1 — indirect
- minimalistic-assert@1.0.1 — indirect
- minimalistic-crypto-utils@1.0.1 — indirect
- mustache@4.0.0 — indirect
- near-abi@0.2.0 — direct
- node-addon-api@5.1.0 — indirect
- node-fetch@2.6.7 — direct
- node-gyp-build@4.8.4 — indirect
- randombytes@2.1.0 — indirect
- safe-buffer@5.2.1 — indirect
- secp256k1@5.0.1 — indirect
- setprototypeof@1.1.1 — indirect
- statuses@1.5.0 — indirect
- toidentifier@1.0.0 — indirect
- tr46@0.0.3 — indirect
- webidl-conversions@3.0.1 — indirect
- whatwg-url@5.0.0 — indirect
- xtend@4.0.2 — indirect
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.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
|---|---|
| Code-Review | 7/10 — Found 6/8 approved changesets -- score normalized to 7 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Security-Policy | 9/10 — security policy file detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 6/10 — binaries present in source code |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-01T11:33:54.458Z
- https://api.deps.dev/v3/systems/npm/packages/near-api-js/versions/5.1.0 — retrieved 2026-11-01T11:33:54.880Z
- https://api.deps.dev/v3/systems/npm/packages/near-api-js/versions/5.1.0:dependencies — retrieved 2026-11-01T11:33:54.952Z
- https://api.deps.dev/v3/projects/github.com%2Fnear%2Fnear-api-js — retrieved 2026-11-01T11:33:55.295Z