hsb2rgb — Greenflagged

HSV (HSB) to RGB color converter

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jankuca

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
email-domain	unclaimed-email:http://jankuca.com	AI (email-domain): The 'email' field contains a URL (the author's personal site), not an actual email address. This is a malformed metadata field from a 12+ year old package, not a domain hijacking risk.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Package is a legitimate single-purpose color conversion utility with 1.7k weekly downloads and real ecosystem usage. Tiny payload and missing metadata are consistent with its age and scope.	ai	2026/04/23

Versions (showing 3 of 3)

Version	Deps	Published
1.0.2	0 / 1	2013-09-03
1.0.1	0 / 1	2013-09-03
1.0.0	0 / 1	2013-09-03

v1.0.2

2 findings

HIGH Unclaimed maintainer email domain: http://jankuca.com email-domain

Maintainer email 'http://jankuca.com' uses domain 'http://jankuca.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.