bare-hrtime
High-resolution timers for 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): bare-hrtime is a native addon that legitimately ships prebuilt platform binaries (.bare files) for the Bare runtime. This is the expected distribution pattern for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 0 / 4 | |
| 2.1.0 | 0 / 4 | |
| 2.0.11 | 0 / 4 | |
| 2.0.10 | 0 / 3 | |
| 2.0.9 | 0 / 2 | |
| 2.0.8 | 0 / 2 | |
| 2.0.7 | 0 / 2 | |
| 2.0.6 | 0 / 2 | |
| 2.0.5 | 0 / 2 | |
| 2.0.4 | 0 / 2 | |
| 2.0.3 | 0 / 2 | |
| 2.0.2 | 0 / 2 | |
| 2.0.1 | 0 / 2 | |
| 2.0.0 | 0 / 2 | |
| 1.0.0 | 0 / 2 |
v2.1.1
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-hrtime.bare • prebuilds/android-arm64/bare-hrtime.bare • prebuilds/android-ia32/bare-hrtime.bare • prebuilds/android-x64/bare-hrtime.bare • prebuilds/darwin-arm64/bare-hrtime.bare • prebuilds/darwin-x64/bare-hrtime.bare • prebuilds/ios-arm64-simulator/bare-hrtime.bare • prebuilds/ios-arm64/bare-hrtime.bare • prebuilds/ios-x64-simulator/bare-hrtime.bare • prebuilds/linux-arm64/bare-hrtime.bare ... and 3 more
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.