react-frame-component — Greenflagged

React component to wrap your application or component in an iFrame for encapsulation purposes

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ryanseddon

Keywords

ReactcomponentiFramebrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Established package with strong publisher track record; missing gitHead is a minor publish-environment change, not a malware indicator. No code or dependency changes from prior version.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Long-established package with strong maintainer track record; lack of Sigstore attestation is a process gap, not a security signal for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Package transitioned to GitHub Actions CI/CD publishing with SLSA provenance attestation; this is a security improvement, not a compromise signal. Stable for this package going forward.	ai	2026/04/23

Versions (showing 51 of 55)

Show 1 prerelease View all versions

Version	Deps	Published
5.3.2	0 / 29	2026-03-29
5.3.1	0 / 29	2026-03-24
5.3.0	0 / 30	2026-03-22
5.2.7	0 / 40	2024-05-30
5.2.6	0 / 40	2023-01-15
5.2.5	0 / 40	2022-12-31
5.2.4	0 / 40	2022-12-19
5.2.3	0 / 40	2022-05-24
5.2.2	0 / 40	2022-05-16
5.2.1	0 / 40	2021-12-08
5.2.0	0 / 40	2021-12-02
5.1.0	0 / 40	2021-06-16
5.0.1	0 / 40	2021-06-11
5.0.0	0 / 40	2021-04-20
4.1.3	0 / 40	2020-07-26
4.1.2	0 / 40	2020-05-06
4.1.1	0 / 40	2019-07-21
4.1.0	0 / 40	2019-03-05
4.0.2	0 / 36	2018-10-09
4.0.1	0 / 36	2018-07-24
4.0.0	0 / 36	2018-06-08
3.0.0	0 / 36	2018-04-18
2.0.2	0 / 38	2018-01-18
2.0.1	0 / 37	2018-01-03
2.0.0	0 / 37	2017-10-09
1.1.1	0 / 37	2017-07-12
1.1.0	0 / 37	2017-06-07
1.0.3	0 / 39	2017-04-10
1.0.2	0 / 39	2017-03-14
1.0.1	0 / 39	2017-02-22
1.0.0	0 / 37	2017-01-22
0.6.6	1 / 12	2016-09-29
0.6.5	1 / 12	2016-08-15
0.6.4	1 / 12	2016-08-08
0.6.3	1 / 12	2016-08-08
0.6.2	1 / 12	2016-07-19
0.6.1	1 / 12	2016-04-28
0.6.0	1 / 12	2016-04-28
0.5.2	1 / 12	2016-02-22
0.5.1	1 / 12	2016-02-14
0.5.0	1 / 12	2016-02-10
0.4.1	1 / 12	2016-01-03
0.4.0	1 / 12	2015-12-03
0.3.5	1 / 10	2015-11-24
0.3.4	1 / 10	2015-07-05
0.3.3	0 / 10	2015-06-04
0.3.2	0 / 10	2015-03-20
0.3.1	0 / 10	2015-03-14
0.3.0	0 / 10	2015-01-13
0.2.2	0 / 10	2014-08-11
0.2.1	1 / 9	2014-08-07

v5.3.2

2 findings

HIGH Publisher changed: ryanseddon → GitHub Actions (on 2026-03-29) provenance

This version was published by a different npm account than previous versions on 2026-03-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v5.3.1

1 finding

LOW No provenance attestation provenance

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

v5.3.0

1 finding

LOW No provenance attestation provenance

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

v5.2.7

1 finding

LOW No provenance attestation provenance

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

v5.2.6

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.2.5

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.2.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.2.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.2.2

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

INFO No provenance attestation provenance

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

v5.2.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: ryanseddon.

INFO No provenance attestation provenance

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

v5.2.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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryanseddon.

v5.1.0

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

LOW No provenance attestation provenance

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

v5.0.1

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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryanseddon.

v5.0.0

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

INFO No provenance attestation provenance

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

v4.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.

v4.1.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.

v4.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.

v4.1.0

1 finding

INFO No provenance attestation provenance

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

v4.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.

v4.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.

v4.0.0

1 finding

INFO No provenance attestation provenance

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