← Home

big-time

npm Repository Homepage

Big time makes it possible to have a timeout that is longer than 24.8 days (2^31-1 milliseconds).

11
Versions
MIT
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

arbcjihrig

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher 'arb' matches the package author (Adam Bretz, [email protected]) and GitHub repo owner (github.com/arb). This is the legitimate project owner, not a takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by a publish from the legitimate project owner (arb) with no code changes; consistent with routine maintenance, not account takeover. ai

Versions (showing 11 of 11)

Version Deps Published
2.0.1 0 / 2
2.0.0 0 / 2
1.1.0 0 / 6
1.0.8 0 / 5
1.0.7 0 / 7
1.0.6 0 / 7
1.0.5 0 / 5
1.0.4 0 / 5
1.0.2 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2

v2.0.1

2 findings
HIGH Publisher changed: cjihrig → arb (on 2018-04-11) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: arb → cjihrig (on 2017-09-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-09-29. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
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.