@rushstack/package-deps-hash 4.7.0

The `package-deps-hash` library generates a JSON object containing the git hashes of all files used to produce a given package. This is useful for scenarios where you want to define a "change receipt" file to be published with a package. The [Rush](http

@rushstack/package-deps-hash@4.7.0 was published on 2026-02-19. 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.

All @rushstack/package-deps-hash versions · Permanent reference to 4.7.0 · Latest release

Package specifications

Version4.7.0
License declarationMIT
Published2026-02-19T00:08:29.917Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size535.14 KiB
Published file count25
Package typeNot declared
ES module entry./lib-esm/index.js
Default entry./lib-commonjs/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies25
Repository starsUnknown
Repository forksUnknown

Install @rushstack/package-deps-hash 4.7.0

npm install @rushstack/package-deps-hash@4.7.0
pnpm add @rushstack/package-deps-hash@4.7.0
yarn add @rushstack/package-deps-hash@4.7.0

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.

Evidence and freshness