ganache-core 2.5.3

[![npm](https://img.shields.io/npm/v/ganache-core.svg)]() [![npm](https://img.shields.io/npm/dm/ganache-core.svg)]() [![Build Status](https://travis-ci.org/trufflesuite/ganache-core.svg?branch=master)](https://travis-ci.org/trufflesuite/ganache-core) [![C

ganache-core@2.5.3 was published on 2019-03-02. Its manifest declares 28 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.9.0.

Deprecated: ganache-core is now ganache; visit https://trfl.io/g7 for details

All ganache-core versions · Permanent reference to 2.5.3 · Latest release

Package specifications

Version2.5.3
License declarationMIT
Published2019-03-02T14:30:55.402Z
Node.js requirement>=8.9.0
Type declarationsNot declared
Runtime dependency count28
Peer requirement count0
Optional dependency count2
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1270.94 KiB
Published file count43
Package typeNot declared
ES module entryNot declared
Default entry./index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies688
Repository stars2621
Repository forks662

Install ganache-core 2.5.3

npm install ganache-core@2.5.3
pnpm add ganache-core@2.5.3
yarn add ganache-core@2.5.3

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

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.

Maintained0/10 — project is archived
Code-Review3/10 — Found 9/29 approved changesets -- score normalized to 3
Dangerous-Workflow10/10 — no dangerous workflow patterns 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-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies5/10 — dependency not pinned by hash detected -- score normalized to 5
License10/10 — license file detected
Fuzzing10/10 — project is fuzzed
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Security-Policy0/10 — security policy file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness