← Home

@tryghost/timezone-data

npm Repository Homepage

`npm install @tryghost/timezone-data --save`

8
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

zimoatghostallouiskernalghostchrisraibleerisdsjohnonolankevinansfieldcobbspuraileencgnjlohminimaluminiumsam-lordpauladamdavisbobvaneckjoeegrigghadretjonhickmanerik-ghostsagzyvershwalmike182ukluissazevedolsingernickmoretonrenatoworksrblstr-ghostevanhahn-ghostweylandswartghost-slimertmciescojonatan-ghost9larsons

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Manual publish by known maintainer, no code changes; not a security signal. ai
provenance publisher-changed-known-maintainer AI (provenance): Known maintainer publishing, already flagged INFO by analyzer. ai
provenance publisher-changed AI (provenance): Ghost Foundation migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this org. ai
maintainer-change maintainer-added AI (maintainer-change): evanhahn-ghost is a Ghost Foundation team member; routine org maintainer rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): ibalosh removal paired with new Ghost team member; consistent with org team change, not takeover. ai

Versions (showing 8 of 108)

Version Deps Published
0.2.6 0 / 10
0.2.5 0 / 10
0.2.4 0 / 10
0.2.3 0 / 10
0.2.2 0 / 10
0.2.1 0 / 10
0.2.0 0 / 10
0.1.1 0 / 11

v0.2.6

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: gargol → kevinansfield (on 2019-07-25, known maintainer) provenance

This version was published by a different npm account (kevinansfield) than the most recent previously approved version (gargol) on 2019-07-25, but kevinansfield is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.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: kevinansfield → gargol (on 2019-06-13, known maintainer) provenance

This version was published by a different npm account (gargol) than the most recent previously approved version (kevinansfield) on 2019-06-13, but gargol is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.4

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: gargol → kevinansfield (on 2019-06-03, known maintainer) provenance

This version was published by a different npm account (kevinansfield) than the most recent previously approved version (gargol) on 2019-06-03, but kevinansfield is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.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: kevinansfield → gargol (on 2019-05-21, known maintainer) provenance

This version was published by a different npm account (gargol) than the most recent previously approved version (kevinansfield) on 2019-05-21, but gargol is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

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: kevinansfield → rishabhgrg (on 2019-04-15, known maintainer) provenance

This version was published by a different npm account (rishabhgrg) than the most recent previously approved version (kevinansfield) on 2019-04-15, but rishabhgrg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.0

1 finding
LOW No provenance attestation provenance

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

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