react-lazy-load — Greenflagged

Simple lazy loading component built with react

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

loktarsergeylaptev

Keywords

reactreactjsreact-componentloadlazy

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): loktar is the stated package author; the repo URL matches loktar00 on GitHub. The transition from sergeylaptev (contributor) to loktar (author) is a legitimate ownership reclaim, not a compromise.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by years; absence of attestation is expected and not a risk signal for this package.	ai	2026/04/24

Versions (showing 26 of 26)

Version	Deps	Published
4.0.1	0 / 19	2022-09-01
4.0.0	4 / 15	2022-08-29
3.1.14	4 / 17	2022-07-15
3.1.13	4 / 17	2020-07-02
3.0.14	4 / 17	2022-07-15
3.0.13	4 / 17	2017-11-30
3.0.12	4 / 17	2017-04-21
3.0.11	3 / 17	2017-02-17
3.0.10	3 / 14	2016-04-13
3.0.9	3 / 14	2016-04-11
3.0.7	3 / 14	2016-03-27
3.0.6	2 / 14	2016-03-17
3.0.5	2 / 14	2016-02-23
3.0.3	2 / 14	2016-02-11
3.0.2	2 / 14	2016-02-11
3.0.1	2 / 14	2016-02-10
3.0.0	2 / 14	2016-01-23
2.0.2	1 / 17	2015-12-22
2.0.1	1 / 15	2015-11-24
2.0.0	1 / 11	2015-11-08
1.0.5	1 / 3	2015-10-20
1.0.4	1 / 1	2015-09-17
1.0.3	1 / 1	2015-07-26
1.0.2	1 / 1	2015-06-18
1.0.1	0 / 1	2015-03-16
1.0.0	0 / 0	2015-02-28

v4.0.0

1 finding

LOW No provenance attestation provenance

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

v3.1.14

1 finding

LOW No provenance attestation provenance

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

v3.1.13

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: sergeylaptev → loktar (on 2020-07-02) provenance

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

v3.0.14

1 finding

INFO No provenance attestation provenance

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

v3.0.13

3 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: sergeylaptev.

INFO No provenance attestation provenance

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

INFO Publisher changed: loktar → sergeylaptev (on 2017-11-30) provenance

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

v3.0.12

1 finding

LOW No provenance attestation provenance

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

v3.0.11

2 findings

HIGH Publisher changed: sergeylaptev → loktar (on 2017-02-17) provenance

This version was published by a different npm account than previous versions on 2017-02-17. 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.

v3.0.10

1 finding

LOW No provenance attestation provenance

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

v3.0.9

1 finding

LOW No provenance attestation provenance

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

v3.0.7

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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