← Home

color-fns

npm Repository

Modern JavaScript color utility library.

13
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

abdelrahman3dlogaretm

Keywords

colorutilityfunctions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed in Jan 2019 (6+ years ago); abdelrahman3d has 15 approved packages, 0 rejected, and has maintained this package stably since the transition. Legitimate historical handoff. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 8+ years old with 13 versions and 9.7k weekly downloads; version 0.0.0 is a historical artifact, not a malicious indicator for this package. ai
bogus-package bogus-package AI (bogus-package): Established package with 3027-day history, 9.7k weekly downloads, and trusted publisher logaretm. Minimal metadata is a legacy characteristic, not a spam indicator. ai
provenance missing-githead AI (provenance): Version diff shows no material changes; missing gitHead is likely a publish environment change, not evidence of tampering. Package has a long clean history. ai
publish-pattern rapid-publish AI (publish-pattern): Rapid publish with no material changes is consistent with a quick metadata fix, not malicious activity. Package has 13 clean versions over 3027 days. ai

Versions (showing 13 of 13)

Version Deps Published
0.1.1 0 / 25
0.1.0 0 / 25
0.0.10 0 / 23
0.0.9 0 / 24
0.0.8 0 / 20
0.0.7 0 / 24
0.0.6 0 / 20
0.0.5 0 / 20
0.0.4 0 / 20
0.0.3 0 / 20
0.0.2 0 / 20
0.0.1 0 / 9
0.0.0 0 / 0

v0.1.1

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: logaretm.

LOW No provenance attestation provenance

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

v0.1.0

3 findings
LOW No provenance attestation provenance

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

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: logaretm.

INFO Publisher changed: abdelrahman3d → logaretm (on 2019-05-23) provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

2 findings
HIGH Publisher changed: logaretm → abdelrahman3d (on 2019-01-13) provenance

This version was published by a different npm account than previous versions on 2019-01-13. 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.0.7

3 findings
HIGH Publisher changed: abdelrahman3d → logaretm (on 2018-07-13) provenance

This version was published by a different npm account than previous versions on 2018-07-13. 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.

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: logaretm.

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

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: logaretm → abdelrahman3d (on 2018-03-27) provenance

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

v0.0.1

2 findings
HIGH Publisher changed: logaretm → abdelrahman3d (on 2018-03-13) provenance

This version was published by a different npm account than previous versions on 2018-03-13. 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.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.