← Home

moment-timezone

npm Repository Homepage

Parse and display moments in any timezone.

22
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

ichernevgilmoreorlesstimrwoodmj1856maggiepintmarwahahaellenaua

Keywords

momentdatetimetimezoneolsonianazonetz

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): ichernev is the original moment-timezone maintainer returning to publish; legitimate publisher transition. ai

Versions (showing 22 of 22)

Version Deps Published
0.6.2 1 / 7
0.6.1 1 / 7
0.6.0 1 / 7
0.5.48 1 / 7
0.5.47 1 / 7
0.5.46 1 / 7
0.5.45 1 / 7
0.5.44 1 / 7
0.5.43 1 / 7
0.5.42 1 / 7
0.5.41 1 / 7
0.5.40 1 / 7
0.5.39 1 / 7
0.5.38 1 / 7
0.5.37 1 / 7
0.5.36 1 / 7
0.5.35 1 / 7
0.0.6 1 / 4
0.0.5 1 / 4
0.0.3 1 / 4
0.0.2 1 / 4
0.0.1 1 / 4

v0.6.2

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.47

1 finding
LOW No provenance attestation provenance

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

v0.5.46

1 finding
LOW No provenance attestation provenance

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

v0.5.45

1 finding
LOW No provenance attestation provenance

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

v0.5.44

1 finding
LOW No provenance attestation provenance

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

v0.5.43

1 finding
LOW No provenance attestation provenance

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

v0.5.42

1 finding
LOW No provenance attestation provenance

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

v0.5.41

1 finding
LOW No provenance attestation provenance

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

v0.5.40

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: ichernev → gilmoreorless (on 2022-12-11) provenance

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

v0.5.39

1 finding
LOW No provenance attestation provenance

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

v0.5.38

1 finding
LOW No provenance attestation provenance

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

v0.5.37

1 finding
LOW No provenance attestation provenance

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

v0.5.36

1 finding
LOW No provenance attestation provenance

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

v0.5.35

2 findings
HIGH Publisher changed: ellenaua → ichernev (on 2022-08-23) provenance

This version was published by a different npm account than previous versions on 2022-08-23. 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.

v0.0.6

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.

v0.0.5

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: timrwood → ichernev (on 2014-04-17) provenance

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

v0.0.3

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: timrwood → ichernev (on 2013-10-10) provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.