near-api-js 5.0.0-next.6

JavaScript library to interact with NEAR Protocol via RPC API

near-api-js@5.0.0-next.6 was published on 2024-08-21. Its manifest declares 15 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.0.0-next.6 · View npm registry JSON · Latest release

Package specifications

Version5.0.0-next.6
License declaration(MIT AND Apache-2.0)
Published2024-08-21T23:40:24.712Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count15
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size86.41 KiB
Published file count198
Package typemodule
ES module entryNot declared
Default entrylib/esm/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies55
Repository stars429
Repository forks267

Install near-api-js 5.0.0-next.6

npm install near-api-js@5.0.0-next.6
pnpm add near-api-js@5.0.0-next.6
yarn add near-api-js@5.0.0-next.6

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.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Code-Review7/10 — Found 6/8 approved changesets -- score normalized to 7
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy9/10 — security policy file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts6/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness