← Home

hsluv

npm Repository Homepage

Human-friendly HSL

6
Versions
MIT
License
No
Install Scripts
Missing
Provenance

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

hsluvcontributors

Keywords

colorcolor spaceCIERGBHSLHSLuvHPLuv

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Legitimate transition from personal 'hsluv' account to 'hsluvcontributors' org account; same project author, same GitHub org, occurred 3+ years ago with clean history since. ai
provenance publisher-changed AI (provenance): Publisher change from hsluv to hsluvcontributors is a legitimate org transition; new publisher has 1300+ day history with 5 approved packages. ai
maintainer-change maintainer-added AI (maintainer-change): hsluvcontributors is the legitimate successor maintainer account for the hsluv project. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of old 'hsluv' account is part of the legitimate transition to 'hsluvcontributors'. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.1 0 / 2
1.0.0 0 / 2
0.1.0 0 / 0
0.0.3 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

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

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (hsluv) were replaced by new maintainers (hsluvcontributors). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: hsluv → hsluvcontributors (on 2022-09-21) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

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: boronine → hsluv (on 2018-02-09) provenance

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

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.