← Home

@react-native/normalize-color

npm Repository Homepage

Color normalization for React Native.

3
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

rsnaracipolleschidmitryrykunfbfkgozalilunaleapsyungsterscortinicoeliwhitehectorramos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): fb is the official Meta/Facebook npm org, not a spam publisher. No keywords/deps are normal for this tiny monorepo utility package. False positive for this package. ai
provenance publisher-changed AI (provenance): dmitryrykun is a known React Native core team member at Meta. Publisher change reflects documented React Native monorepo team transition, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (rsnara, cipolleschi, dmitryrykun, fb, fkgozali) are all known Meta/React Native team members. Expansion reflects organizational monorepo restructuring. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by activity matches the documented React Native monorepo package extraction timeline, not an account takeover pattern. ai

Versions (showing 3 of 3)

Version Deps Published
2.1.0 0 / 0
2.0.0 0 / 0
1.0.0 0 / 0

v2.1.0

2 findings
HIGH Publisher changed: yungsters → dmitryrykun (on 2022-11-03) provenance

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

v2.0.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: cpojer → yungsters (on 2021-08-31) provenance

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

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.