@editframe/react
React bindings for Editframe Elements.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established package with 220 versions; empty description is a cosmetic issue, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions; no provenance is common and not a risk indicator for this package. | ai | |
| dependencies | unvetted-dep:@react-three/offscreen | AI (dependencies): @react-three/offscreen is a legitimate pmndrs/React Three Fiber utility; expected dependency for a 3D React package. | ai | |
| phantom-deps | phantom-dep:@lit/task | AI (phantom-deps): @lit/task is a declared runtime dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mitt | AI (phantom-deps): mitt is a declared runtime dependency; phantom-dep fires because it's not directly imported in the analyzed entry point, not because it's missing. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.57.5 | 3 / 13 | |
| 0.57.4 | 3 / 13 | |
| 0.57.3 | 3 / 13 | |
| 0.57.2 | 3 / 13 | |
| 0.57.1 | 3 / 13 | |
| 0.57.0 | 3 / 13 | |
| 0.56.0 | 3 / 13 | |
| 0.55.2 | 3 / 13 | |
| 0.55.1 | 3 / 13 | |
| 0.55.0 | 3 / 13 | |
| 0.54.2 | 3 / 13 | |
| 0.54.1 | 3 / 13 | |
| 0.54.0 | 3 / 13 | |
| 0.53.3 | 3 / 13 | |
| 0.53.2 | 3 / 13 | |
| 0.53.1 | 3 / 13 | |
| 0.53.0 | 3 / 13 | |
| 0.52.1 | 3 / 13 | |
| 0.52.0 | 3 / 13 | |
| 0.51.9 | 3 / 13 | |
| 0.51.8 | 3 / 13 | |
| 0.51.7 | 3 / 13 | |
| 0.51.6 | 3 / 13 | |
| 0.51.5 | 3 / 13 | |
| 0.51.4 | 3 / 13 | |
| 0.51.3 | 3 / 13 | |
| 0.51.2 | 3 / 13 | |
| 0.51.1 | 3 / 13 | |
| 0.50.1 | 3 / 13 | |
| 0.50.0 | 3 / 13 | |
| 0.49.7 | 3 / 13 | |
| 0.49.6 | 3 / 13 | |
| 0.49.5 | 3 / 13 | |
| 0.49.4 | 3 / 13 | |
| 0.49.3 | 3 / 13 | |
| 0.49.2 | 3 / 13 | |
| 0.49.1 | 3 / 13 | |
| 0.49.0 | 3 / 13 | |
| 0.48.1 | 3 / 13 | |
| 0.48.0 | 3 / 13 | |
| 0.47.2 | 3 / 13 | |
| 0.47.1 | 3 / 13 | |
| 0.47.0 | 3 / 13 | |
| 0.46.4 | 3 / 13 | |
| 0.46.2 | 3 / 13 | |
| 0.46.1 | 3 / 13 | |
| 0.46.0 | 3 / 13 | |
| 0.45.8 | 3 / 13 | |
| 0.45.6 | 3 / 13 | |
| 0.45.5 | 3 / 13 | |
| 0.45.4 | 3 / 13 |
v0.57.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.