umi 2.6.0

Pluggable enterprise-level react application framework.

umi@2.6.0 was published on 2019-03-07. Its manifest declares 17 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All umi versions · Permanent reference to 2.6.0 · Latest release

Package specifications

Version2.6.0
License declarationMIT
Published2019-03-07T06:49:34.151Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count17
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size49.63 KiB
Published file count55
Package typeNot declared
ES module entryindex.js
Default entryNot declared
Side effects declaration["./lib/renderRoutes.js"]
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars16043
Repository forks2655

Install umi 2.6.0

npm install umi@2.6.0
pnpm add umi@2.6.0
yarn add umi@2.6.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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.

Maintained10/10 — 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Code-Review0/10 — Found 2/30 approved changesets -- score normalized to 0
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Binary-Artifacts9/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness