← Home

hex-rgba

npm Repository Homepage

Convert HEX to RGBA

3
Versions
ISC
License
No
Install Scripts
Missing
Provenance

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

developersoul

Keywords

hexrgbaconvertcolors

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Package is ~11 years old with consistent publisher; missing gitHead reflects a publish environment change, not a supply chain compromise. No other risk signals present. ai
provenance no-provenance AI (provenance): Established package predating Sigstore provenance; absence of attestation is expected for packages of this age and is not a security risk. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.2 0 / 2
1.0.1 0 / 1
1.0.0 0 / 1

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.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: developersoul.

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.