history
Manage session history with JavaScript
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a declared runtime dependency used as a Babel helper; it's loaded by convention and not directly imported. This is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): history is a long-established package from a highly reputable publisher; lack of Sigstore provenance is a best-practice gap, not a security risk for this package. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 1 / 0 | |
| 5.2.0 | 1 / 0 | |
| 5.1.0 | 1 / 0 | |
| 5.0.3 | 1 / 0 | |
| 5.0.2 | 1 / 0 | |
| 5.0.1 | 1 / 0 | |
| 5.0.0 | 1 / 0 | |
| 4.10.1 | 6 / 29 | |
| 4.10.0 | 6 / 29 | |
| 4.9.0 | 6 / 29 | |
| 4.7.2 | 5 / 26 | |
| 4.7.1 | 5 / 26 | |
| 4.7.0 | 5 / 26 | |
| 4.6.3 | 5 / 26 | |
| 4.6.2 | 5 / 26 | |
| 4.6.1 | 5 / 26 | |
| 4.6.0 | 5 / 26 | |
| 4.5.1 | 5 / 25 | |
| 4.5.0 | 5 / 27 | |
| 4.4.1 | 5 / 27 | |
| 4.4.0 | 5 / 27 | |
| 4.3.0 | 4 / 27 | |
| 4.2.1 | 3 / 27 | |
| 4.2.0 | 3 / 27 | |
| 4.1.0 | 3 / 27 | |
| 4.0.1 | 3 / 27 | |
| 4.0.0 | 3 / 27 | |
| 3.3.0 | 4 / 27 | |
| 3.2.1 | 4 / 27 | |
| 3.2.0 | 4 / 27 | |
| 3.1.0 | 4 / 27 | |
| 3.0.0 | 3 / 28 | |
| 2.1.2 | 4 / 24 | |
| 2.1.1 | 4 / 24 | |
| 2.1.0 | 4 / 24 | |
| 2.0.2 | 4 / 24 | |
| 2.0.1 | 4 / 24 | |
| 2.0.0 | 4 / 26 | |
| 1.17.0 | 4 / 26 | |
| 1.16.0 | 4 / 26 | |
| 1.15.0 | 4 / 26 | |
| 1.14.0 | 4 / 26 | |
| 1.13.1 | 4 / 26 | |
| 1.13.0 | 4 / 23 | |
| 1.12.6 | 4 / 22 | |
| 1.12.5 | 4 / 22 | |
| 1.12.4 | 4 / 22 | |
| 1.12.3 | 4 / 20 | |
| 1.12.2 | 4 / 20 | |
| 1.12.1 | 4 / 20 | |
| 1.12.0 | 4 / 20 |
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mjackson.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mjackson.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.