bare-timers No license 7 versions

bare-timers

npm Repository Homepage

7

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mafintoshkasperisager

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): Native addon package; prebuilt binaries for multiple platforms are the documented distribution pattern for bare-timers.	ai	2026/05/22

Versions (showing 7 of 7)

Version	Deps	Published
3.2.1	0 / 5	2026-02-17
3.2.0	0 / 5	2025-11-06
3.1.2	0 / 4	2025-10-06
3.1.1	0 / 4	2025-09-22
3.1.0	0 / 4	2025-09-22
3.0.3	1 / 4	2025-09-01
3.0.2	1 / 4	2025-06-25

v3.2.1

2 findings

HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-timers.bare • prebuilds/android-arm64/bare-timers.bare • prebuilds/android-ia32/bare-timers.bare • prebuilds/android-x64/bare-timers.bare • prebuilds/darwin-arm64/bare-timers.bare • prebuilds/darwin-x64/bare-timers.bare • prebuilds/ios-arm64-simulator/bare-timers.bare • prebuilds/ios-arm64/bare-timers.bare • prebuilds/ios-x64-simulator/bare-timers.bare • prebuilds/linux-arm64/bare-timers.bare ... and 3 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.0

2 findings

HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-timers.bare • prebuilds/android-arm64/bare-timers.bare • prebuilds/android-ia32/bare-timers.bare • prebuilds/android-x64/bare-timers.bare • prebuilds/darwin-arm64/bare-timers.bare • prebuilds/darwin-x64/bare-timers.bare • prebuilds/ios-arm64-simulator/bare-timers.bare • prebuilds/ios-arm64/bare-timers.bare • prebuilds/ios-x64-simulator/bare-timers.bare • prebuilds/linux-arm64/bare-timers.bare ... and 3 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.2

2 findings

HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-timers.bare • prebuilds/android-arm64/bare-timers.bare • prebuilds/android-ia32/bare-timers.bare • prebuilds/android-x64/bare-timers.bare • prebuilds/darwin-arm64/bare-timers.bare • prebuilds/darwin-x64/bare-timers.bare • prebuilds/ios-arm64-simulator/bare-timers.bare • prebuilds/ios-arm64/bare-timers.bare • prebuilds/ios-x64-simulator/bare-timers.bare • prebuilds/linux-arm64/bare-timers.bare ... and 3 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.1

2 findings

HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-timers.bare • prebuilds/android-arm64/bare-timers.bare • prebuilds/android-ia32/bare-timers.bare • prebuilds/android-x64/bare-timers.bare • prebuilds/darwin-arm64/bare-timers.bare • prebuilds/darwin-x64/bare-timers.bare • prebuilds/ios-arm64-simulator/bare-timers.bare • prebuilds/ios-arm64/bare-timers.bare • prebuilds/ios-x64-simulator/bare-timers.bare • prebuilds/linux-arm64/bare-timers.bare ... and 3 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.0

2 findings

HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-timers.bare • prebuilds/android-arm64/bare-timers.bare • prebuilds/android-ia32/bare-timers.bare • prebuilds/android-x64/bare-timers.bare • prebuilds/darwin-arm64/bare-timers.bare • prebuilds/darwin-x64/bare-timers.bare • prebuilds/ios-arm64-simulator/bare-timers.bare • prebuilds/ios-arm64/bare-timers.bare • prebuilds/ios-x64-simulator/bare-timers.bare • prebuilds/linux-arm64/bare-timers.bare ... and 3 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.3

2 findings

HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-timers.bare • prebuilds/android-arm64/bare-timers.bare • prebuilds/android-ia32/bare-timers.bare • prebuilds/android-x64/bare-timers.bare • prebuilds/darwin-arm64/bare-timers.bare • prebuilds/darwin-x64/bare-timers.bare • prebuilds/ios-arm64-simulator/bare-timers.bare • prebuilds/ios-arm64/bare-timers.bare • prebuilds/ios-x64-simulator/bare-timers.bare • prebuilds/linux-arm64/bare-timers.bare ... and 3 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.2

2 findings

HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-timers.bare • prebuilds/android-arm64/bare-timers.bare • prebuilds/android-ia32/bare-timers.bare • prebuilds/android-x64/bare-timers.bare • prebuilds/darwin-arm64/bare-timers.bare • prebuilds/darwin-x64/bare-timers.bare • prebuilds/ios-arm64-simulator/bare-timers.bare • prebuilds/ios-arm64/bare-timers.bare • prebuilds/ios-x64-simulator/bare-timers.bare • prebuilds/linux-arm64/bare-timers.bare ... and 3 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.