@solana/rpc-core 2.0.0-development

A library for making calls to the Solana JSON RPC API

@solana/rpc-core@2.0.0-development was published on 2024-01-24. Its manifest declares 8 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 @solana/rpc-core versions · Permanent reference to 2.0.0-development · Latest release

Package specifications

Version2.0.0-development
License declarationMIT
Published2024-01-24T04:18:48.270Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count8
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size593.07 KiB
Published file count168
Package typemodule
ES module entry./dist/index.node.js
Default entry./dist/index.node.cjs
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies12
Repository stars2780
Repository forks1092

Install @solana/rpc-core 2.0.0-development

npm install @solana/rpc-core@2.0.0-development
pnpm add @solana/rpc-core@2.0.0-development
yarn add @solana/rpc-core@2.0.0-development

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.

Maintained2/10 — 0 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 2
Code-Review5/10 — Found 9/17 approved changesets -- score normalized to 5
Security-Policy10/10 — security policy file detected
Binary-Artifacts9/10 — binaries present in source code
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
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Branch-Protection8/10 — branch protection is not maximal on development and all release branches

Evidence and freshness