react-fast-compare
Fastest deep equal comparison for React. Great for React.memo & shouldComponentUpdate. Also really fast general-purpose deep comparison.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:michaelmerrill.io | AI (email-domain): Maintainer is a FormidableLabs team member; domain lapse is low-risk given organizational context and the actual publisher is chrisbolin with strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer changes reflect FormidableLabs team reorganization; publisher chrisbolin is consistent and trusted. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from chrisbolin to kale-stew reflects legitimate FormidableLabs org transition; kale-stew has strong track record (745 approved, 0 rejected). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are FormidableLabs team members; consistent with org-level maintenance of this package. | ai | |
| provenance | no-provenance | AI (provenance): Pre-provenance-era package from a trusted publisher; absence of Sigstore attestation is expected and not a security concern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 0 / 46 | |
| 3.2.1 | 0 / 44 | |
| 3.2.0 | 0 / 43 | |
| 3.1.1 | 0 / 34 | |
| 3.1.0 | 0 / 34 | |
| 3.0.2 | 0 / 29 | |
| 3.0.1 | 0 / 29 | |
| 3.0.0 | 0 / 29 | |
| 2.0.4 | 0 / 27 | |
| 2.0.3 | 0 / 27 | |
| 2.0.2 | 0 / 27 | |
| 2.0.1 | 0 / 27 | |
| 2.0.0 | 0 / 27 | |
| 1.0.0 | 0 / 13 |
v3.2.1
2 findingsThis version was published by a different npm account than previous versions on 2023-03-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2020-05-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2020-05-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsMaintainer email '[email protected]' uses domain 'michaelmerrill.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
3 findingsMaintainer email '[email protected]' uses domain 'michaelmerrill.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-09. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.2
2 findingsMaintainer email '[email protected]' uses domain 'michaelmerrill.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-06-25. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-06-04. This could indicate a legitimate maintainer transition or an account compromise.