@tryghost/kg-unsplash-selector MIT 54 versions

@tryghost/kg-unsplash-selector

npm Repository

Unsplash Selector in React

54

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

zimoatghostallouiskernalghostchrisraibleerisdsjohnonolankevinansfieldcobbspuraileencgnjlohminimaluminiumsam-lordpauladamdavisbobvaneckjoeegrigghadretjonhickmanerik-ghostsagzyvershwalzach1618mike182ukluissazevedolsingernickmoretonrenatoworksrblstr-ghostevanhahn-ghostweylandswartghost-slimertmciescojonatan-ghost9larsons

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): CI monorepo publish quirk; SLSA attestation still present, no behavior change.	ai	2026/07/10
npm-metadata	no-description	AI (npm-metadata): Common across TryGhost internal sub-packages; not a malware indicator here.	ai	2026/07/10

Versions (showing 54 of 54)

Version	Deps	Published
0.4.5	0 / 0	2026-07-17
0.4.4	0 / 23	2026-07-10
0.4.3	0 / 23	2026-06-22
0.4.2	0 / 23	2026-06-02
0.4.1	0 / 23	2026-04-27
0.4.0	0 / 23	2026-04-20
0.3.26	0 / 23	2026-04-02
0.3.25	0 / 23	2026-03-23
0.3.24	0 / 23	2026-03-23
0.3.23	0 / 23	2026-03-22
0.3.22	0 / 23	2026-03-20
0.3.21	0 / 21	2026-03-16
0.3.20	0 / 22	2026-03-12
0.3.19	0 / 23	2026-03-02
0.3.18	0 / 23	2026-02-26
0.3.17	0 / 23	2026-02-23
0.3.16	0 / 23	2026-02-18
0.3.15	0 / 23	2026-02-12
0.3.14	0 / 23	2026-02-12
0.3.13	0 / 23	2026-02-05
0.3.12	0 / 23	2026-01-27
0.3.11	0 / 23	2026-01-22
0.3.10	0 / 23	2026-01-15
0.3.9	0 / 23	2026-01-05
0.3.7	0 / 23	2025-11-19
0.3.6	0 / 23	2025-06-24
0.3.5	0 / 23	2025-06-19
0.3.4	0 / 23	2025-05-27
0.3.3	0 / 23	2025-05-12
0.3.2	0 / 23	2025-05-07
0.3.0	0 / 23	2025-02-17
0.2.8	0 / 23	2025-01-29
0.2.7	0 / 23	2025-01-08
0.2.6	0 / 23	2024-10-31
0.2.5	0 / 23	2024-09-19
0.2.4	0 / 23	2024-09-03
0.2.3	0 / 23	2024-08-12
0.2.2	0 / 23	2024-08-12
0.2.1	0 / 23	2024-07-01
0.2.0	0 / 23	2024-05-29
0.1.17	0 / 23	2024-05-16
0.1.16	0 / 23	2024-05-16
0.1.15	0 / 23	2024-05-14
0.1.14	0 / 23	2024-05-14
0.1.13	0 / 23	2024-04-16
0.1.12	0 / 23	2024-03-25
0.1.11	0 / 23	2024-03-12
0.1.10	0 / 22	2024-03-12
0.1.9	0 / 22	2024-03-12
0.1.8	0 / 22	2024-03-12
0.1.7	0 / 21	2024-03-12
0.1.6	0 / 21	2024-03-12
0.1.1	0 / 21	2024-03-12
0.1.0	0 / 21	2024-03-12

v0.4.5

2 findings

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v0.4.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.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: kevinansfield → daniellockyer (on 2025-02-17, known maintainer) provenance

This version was published by a different npm account (daniellockyer) than the most recent previously approved version (kevinansfield) on 2025-02-17, but daniellockyer 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.8

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: ronaldlangeveld → kevinansfield (on 2025-01-29, known maintainer) provenance

This version was published by a different npm account (kevinansfield) than the most recent previously approved version (ronaldlangeveld) on 2025-01-29, 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.7

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: ronaldlangeveld → kevinansfield (on 2025-01-08, known maintainer) provenance

This version was published by a different npm account (kevinansfield) than the most recent previously approved version (ronaldlangeveld) on 2025-01-08, 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.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: vershwal → ronaldlangeveld (on 2024-10-31, known maintainer) provenance

This version was published by a different npm account (ronaldlangeveld) than the most recent previously approved version (vershwal) on 2024-10-31, but ronaldlangeveld 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

1 finding

LOW No provenance attestation provenance

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

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: kevinansfield → vershwal (on 2024-09-03, known maintainer) provenance

This version was published by a different npm account (vershwal) than the most recent previously approved version (kevinansfield) on 2024-09-03, but vershwal 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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.16

1 finding

LOW No provenance attestation provenance

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

v0.1.15

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

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

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: ronaldlangeveld → kevinansfield (on 2024-04-16, known maintainer) provenance

This version was published by a different npm account (kevinansfield) than the most recent previously approved version (ronaldlangeveld) on 2024-04-16, 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.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

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

1 finding

LOW No provenance attestation provenance

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

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