@zendesk/zcli-themes — Greenflagged

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

sunesimonsenavecerektoken-cjgbilljhzdrsimzdbpetersonluis-almeidafrederickzhmassakizd-svc-npmjsromeo-zdakash.lahaneaishwaryakannan12345savya.singhraj.hawaldargabor.vassneeraj.gupta-zendeskzendesk-berengamble

Keywords

zclizendeskclicommand

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/ws	AI (phantom-deps): @types packages are type-only and conventionally listed as deps in TS projects; not a real phantom dep.	ai	2026/06/05
phantom-deps	phantom-dep:@types/inquirer	AI (phantom-deps): Same as @types/ws — type-only package, stable false positive for this TS project.	ai	2026/06/05

Versions (showing 2 of 2)

Version	Deps	Published
1.1.0	11 / 13	2026-06-04
1.0.0	11 / 13	2026-04-23

v1.1.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: massaki → zd-svc-npmjs (on 2026-06-04, known maintainer) provenance

This version was published by a different npm account (zd-svc-npmjs) than the most recent previously approved version (massaki) on 2026-06-04, but zd-svc-npmjs 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.