nanotiming
Small timing library
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change yoshuawuyts→goto-bus-stop occurred in 2018 as a known choojs ecosystem handoff. goto-bus-stop has 1219 approved packages and is a core contributor. Stable historical fact. | ai | |
| phantom-deps | phantom-dep:nanoassert | AI (phantom-deps): nanoassert is used as a browser field alias for the 'assert' module, not via direct require(). This is a legitimate browser polyfill pattern, not a phantom dependency. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 7.3.1 | 2 / 4 | |
| 7.3.0 | 1 / 4 | |
| 7.2.0 | 1 / 4 | |
| 7.1.0 | 1 / 4 | |
| 7.0.0 | 0 / 4 | |
| 6.1.5 | 0 / 4 | |
| 6.1.4 | 0 / 4 | |
| 6.1.3 | 1 / 4 | |
| 6.1.2 | 1 / 4 | |
| 6.1.1 | 1 / 4 | |
| 6.1.0 | 1 / 4 | |
| 6.0.0 | 1 / 4 | |
| 5.2.1 | 0 / 4 | |
| 5.2.0 | 0 / 4 | |
| 5.1.0 | 0 / 4 | |
| 5.0.0 | 0 / 4 | |
| 4.0.0 | 0 / 4 | |
| 3.0.2 | 0 / 4 | |
| 3.0.1 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.0.0 | 0 / 4 | |
| 1.0.1 | 0 / 4 | |
| 1.0.0 | 0 / 4 |
v7.3.1
2 findingsThis version was published by a different npm account than previous versions on 2018-04-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-04. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-07-09. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-07-05. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.