casper-js-sdk

SDK to interact with the Casper blockchain

casper-js-sdk@5.3.1 was published on 2026-11-02. Its manifest declares 15 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.

All casper-js-sdk versions · Permanent reference to 5.3.1 · View npm registry JSON

Package specifications

Version5.3.1
License declarationApache 2.0
Published2026-11-02T16:29:16.144Z
Node.js requirement>=18
Type declarationsBundled declarations
Runtime dependency count15
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size7570.03 KiB
Published file count169
Package typeNot declared
ES module entryNot declared
Default entrydist/lib.node.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies52
Repository stars74
Repository forks58

Install casper-js-sdk 5.3.1

npm install casper-js-sdk@5.3.1
pnpm add casper-js-sdk@5.3.1
yarn add casper-js-sdk@5.3.1

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.

Code-Review8/10 — Found 8/10 approved changesets -- score normalized to 8
Maintained10/10 — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts7/10 — binaries present in source code
Pinned-Dependencies5/10 — dependency not pinned by hash detected -- score normalized to 5
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Security-Policy0/10 — security policy file not detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness