get-starknet-core 4.0.0-next.5
[](https://www.npmjs.com/package/get-starknet)
get-starknet-core@4.0.0-next.5 was published on 2024-04-25. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: Package no longer supported. Please use @starknet-io/get-starknet-core
All get-starknet-core versions · Permanent reference to 4.0.0-next.5 · View npm registry JSON · Latest release
Package specifications
| Version | 4.0.0-next.5 |
|---|---|
| License declaration | MIT |
| Published | 2024-04-25T13:40:52.549Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 28.27 KiB |
| Published file count | 15 |
| Package type | module |
| ES module entry | ./dist/core.js |
| Default entry | ./dist/core.umd.cjs |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install get-starknet-core 4.0.0-next.5
npm install get-starknet-core@4.0.0-next.5 pnpm add get-starknet-core@4.0.0-next.5 yarn add get-starknet-core@4.0.0-next.5
Runtime dependencies
- starknet-types ^0.7.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.
- starknet-types@0.7.2 — 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
- Readable npm registry JSON — retrieved 2026-11-08T04:01:23.691Z
- https://api.deps.dev/v3/systems/npm/packages/get-starknet-core/versions/4.0.0-next.5 — retrieved 2026-11-08T04:01:23.773Z
- https://api.deps.dev/v3/systems/npm/packages/get-starknet-core/versions/4.0.0-next.5:dependencies — retrieved 2026-11-08T04:01:23.801Z