react-frame-component
React component to wrap your application or component in an iFrame for encapsulation purposes
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 |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 5.3.2 | 0 / 29 | |
| 5.3.1 | 0 / 29 | |
| 5.3.0 | 0 / 30 | |
| 5.2.7 | 0 / 40 | |
| 5.2.6 | 0 / 40 | |
| 5.2.5 | 0 / 40 | |
| 5.2.4 | 0 / 40 | |
| 5.2.3 | 0 / 40 | |
| 5.2.2 | 0 / 40 | |
| 5.2.1 | 0 / 40 | |
| 5.2.0 | 0 / 40 | |
| 5.1.0 | 0 / 40 | |
| 5.0.1 | 0 / 40 | |
| 5.0.0 | 0 / 40 | |
| 4.1.3 | 0 / 40 | |
| 4.1.2 | 0 / 40 | |
| 4.1.1 | 0 / 40 | |
| 4.1.0 | 0 / 40 | |
| 4.0.2 | 0 / 36 | |
| 4.0.1 | 0 / 36 | |
| 4.0.0 | 0 / 36 | |
| 3.0.0 | 0 / 36 | |
| 2.0.2 | 0 / 38 | |
| 2.0.1 | 0 / 37 | |
| 2.0.0 | 0 / 37 | |
| 1.1.1 | 0 / 37 | |
| 1.1.0 | 0 / 37 | |
| 1.0.3 | 0 / 39 | |
| 1.0.2 | 0 / 39 | |
| 1.0.1 | 0 / 39 | |
| 1.0.0 | 0 / 37 | |
| 0.6.6 | 1 / 12 | |
| 0.6.5 | 1 / 12 | |
| 0.6.4 | 1 / 12 | |
| 0.6.3 | 1 / 12 | |
| 0.6.2 | 1 / 12 | |
| 0.6.1 | 1 / 12 | |
| 0.6.0 | 1 / 12 | |
| 0.5.2 | 1 / 12 | |
| 0.5.1 | 1 / 12 | |
| 0.5.0 | 1 / 12 | |
| 0.4.1 | 1 / 12 | |
| 0.4.0 | 1 / 12 | |
| 0.3.5 | 1 / 10 | |
| 0.3.4 | 1 / 10 | |
| 0.3.3 | 0 / 10 | |
| 0.3.2 | 0 / 10 | |
| 0.3.1 | 0 / 10 | |
| 0.3.0 | 0 / 10 | |
| 0.2.2 | 0 / 10 | |
| 0.2.1 | 1 / 9 | |
| 0.2.0 | 1 / 9 | |
| 0.1.2 | 1 / 9 | |
| 0.1.1 | 1 / 9 | |
| 0.1.0 | 1 / 8 |
v5.3.2
2 findingsThis 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.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryanseddon.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryanseddon.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryanseddon.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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 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 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryanseddon.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.