umi-webpack-bundle-analyzer

Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap

umi-webpack-bundle-analyzer@4.4.2 was published on 2021-06-24. Its manifest declares 10 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 10.13.0.

All umi-webpack-bundle-analyzer versions · Permanent reference to 4.4.2

Package specifications

Version4.4.2
License declarationMIT
Published2021-06-24T09:22:11.964Z
Node.js requirement>= 10.13.0
Type declarationsNot declared
Runtime dependency count10
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1274.88 KiB
Published file count43
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies23
Repository stars11
Repository forks3

Install umi-webpack-bundle-analyzer 4.4.2

npm install umi-webpack-bundle-analyzer@4.4.2
pnpm add umi-webpack-bundle-analyzer@4.4.2
yarn add umi-webpack-bundle-analyzer@4.4.2

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Code-Review0/10 — Found 1/29 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
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