umi-history
Manage session history with JavaScript
umi-history@0.1.2 was published on 2018-01-16. Its manifest declares 6 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-history versions · Permanent reference to 0.1.2
Package specifications
| Version | 0.1.2 |
|---|---|
| License declaration | MIT |
| Published | 2018-01-16T07:55:26.293Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 6 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | es/index.js |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 10 |
| Repository stars | 8294 |
| Repository forks | 950 |
Install umi-history 0.1.2
npm install umi-history@0.1.2 pnpm add umi-history@0.1.2 yarn add umi-history@0.1.2
Runtime dependencies
- invariant ^2.2.1
- loose-envify ^1.2.0
- resolve-pathname ^2.2.0
- value-equal ^0.4.0
- query-string ^5.0.1
- warning ^3.0.0
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.
- decode-uri-component@0.2.2 — indirect
- invariant@2.2.4 — direct
- js-tokens@4.0.0 — indirect
- loose-envify@1.4.0 — direct
- object-assign@4.1.1 — indirect
- query-string@5.1.1 — direct
- resolve-pathname@2.2.0 — direct
- strict-uri-encode@1.1.0 — indirect
- value-equal@0.4.0 — direct
- warning@3.0.0 — 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.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 1/10 — Found 4/28 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 3/10 — dependency not pinned by hash detected -- score normalized to 3 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/umi-history/0.1.2 — retrieved 2026-10-29T14:15:13.824Z
- https://api.deps.dev/v3/systems/npm/packages/umi-history/versions/0.1.2 — retrieved 2026-10-29T14:15:14.408Z
- https://api.deps.dev/v3/systems/npm/packages/umi-history/versions/0.1.2:dependencies — retrieved 2026-10-29T14:15:14.431Z
- https://api.deps.dev/v3/projects/github.com%2FReactTraining%2Fhistory — retrieved 2026-10-29T14:15:14.551Z