react-error-overlay — Greenflagged

An overlay for displaying stack frames.

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

fbtimeriansuianschmitzrickhanlonii

Keywords

overlaysyntaxerrorredboxredboxcrashwarning

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Legacy CRA monorepo package predates Sigstore provenance; stable false positive for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within the facebook/create-react-app team; both ianschmitz and iansu are known CRA maintainers.	ai	2026/04/24

Versions (showing 45 of 45)

Version	Deps	Published
6.1.0	0 / 23	2025-02-15
6.0.11	0 / 25	2022-04-12
6.0.10	0 / 25	2021-12-14
6.0.9	0 / 34	2021-02-03
6.0.8	0 / 34	2020-10-23
6.0.7	0 / 31	2020-03-21
6.0.6	0 / 31	2020-02-14
6.0.5	0 / 31	2020-01-31
6.0.4	0 / 31	2019-12-05
6.0.3	0 / 31	2019-10-03
6.0.2	0 / 31	2019-09-19
6.0.1	0 / 31	2019-08-13
6.0.0	0 / 31	2019-08-09
5.1.6	0 / 31	2019-05-08
5.1.5	0 / 31	2019-04-22
5.1.4	0 / 32	2019-03-06
5.1.3	0 / 32	2019-02-10
5.1.2	0 / 32	2019-01-04
5.1.1	0 / 32	2018-12-23
5.1.0	0 / 32	2018-11-01
5.0.6	0 / 32	2018-10-30
5.0.5	0 / 32	2018-10-14
5.0.4	0 / 32	2018-10-03
5.0.3	0 / 32	2018-10-02
5.0.2	0 / 32	2018-10-01
5.0.1	0 / 31	2018-09-28
5.0.0	0 / 32	2018-09-26
4.0.1	0 / 29	2018-08-22
4.0.0	0 / 29	2018-01-15
3.0.0	0 / 29	2017-10-30
2.0.2	8 / 14	2017-09-27
2.0.1	8 / 13	2017-09-02
2.0.0	8 / 13	2017-08-28
1.0.10	6 / 13	2017-08-09
1.0.9	6 / 13	2017-06-29
1.0.8	6 / 13	2017-06-28
1.0.7	6 / 13	2017-05-27
1.0.6	6 / 13	2017-05-24
1.0.5	6 / 13	2017-05-22
1.0.4	6 / 13	2017-05-22
1.0.3	6 / 13	2017-05-21
1.0.2	6 / 13	2017-05-20
1.0.1	6 / 13	2017-05-19
1.0.0	5 / 13	2017-05-19
0.0.0	0 / 0	2017-05-10

v6.0.11

1 finding

LOW No provenance attestation provenance

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

v6.0.10

1 finding

LOW No provenance attestation provenance

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

v6.0.8

1 finding

LOW No provenance attestation provenance

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

v6.0.7

1 finding

LOW No provenance attestation provenance

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

v6.0.6

1 finding

LOW No provenance attestation provenance

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

v6.0.5

1 finding

LOW No provenance attestation provenance

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

v6.0.4

1 finding

LOW No provenance attestation provenance

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

v6.0.3

1 finding

LOW No provenance attestation provenance

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

v6.0.2

1 finding

LOW No provenance attestation provenance

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

v6.0.1

1 finding

LOW No provenance attestation provenance

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

v6.0.0

1 finding

LOW No provenance attestation provenance

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

v5.1.6

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

LOW No provenance attestation provenance

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

v5.1.5

1 finding

LOW No provenance attestation provenance

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

v5.1.4

2 findings

HIGH Publisher changed: ianschmitz → iansu (on 2019-03-06) provenance

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

v5.1.3

1 finding

INFO No provenance attestation provenance

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

v5.1.2

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: timer → ianschmitz (on 2019-01-04) provenance

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

v5.1.1

1 finding

INFO No provenance attestation provenance

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

v5.1.0

1 finding

LOW No provenance attestation provenance

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

v5.0.6

1 finding

LOW No provenance attestation provenance

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

v5.0.5

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: timer → gaearon (on 2018-10-14) provenance

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

v5.0.4

1 finding

INFO No provenance attestation provenance

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

v5.0.3

1 finding

INFO No provenance attestation provenance

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

v5.0.2

1 finding

INFO No provenance attestation provenance

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

v5.0.1

1 finding

INFO No provenance attestation provenance

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

v5.0.0

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: gaearon → timer (on 2018-09-26) provenance

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