@expofp/renderer
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:meshoptimizer | AI (phantom-deps): 3D renderer package; meshoptimizer is a legitimate mesh optimization dep used via build config, not direct import. | ai | |
| phantom-deps | phantom-dep:hold-event | AI (phantom-deps): hold-event is a legitimate runtime dep used in 3D input handling; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:camera-controls | AI (phantom-deps): camera-controls is declared in dependencies; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 8 / 6 | |
| 3.1.6 | 7 / 6 | |
| 3.1.5 | 7 / 6 | |
| 3.1.4 | 7 / 6 | |
| 3.1.3 | 7 / 6 | |
| 3.1.2 | 7 / 6 | |
| 3.1.1 | 7 / 7 | |
| 3.1.0 | 7 / 7 | |
| 3.0.1 | 7 / 7 | |
| 3.0.0 | 7 / 9 | |
| 2.3.3 | 7 / 7 | |
| 2.3.2 | 7 / 9 | |
| 2.3.1 | 7 / 9 | |
| 2.3.0 | 7 / 9 | |
| 2.2.1 | 7 / 9 | |
| 2.2.0 | 7 / 9 | |
| 2.1.2 | 7 / 9 | |
| 2.1.1 | 7 / 9 | |
| 2.1.0 | 7 / 9 | |
| 2.0.1 | 7 / 9 | |
| 2.0.0 | 6 / 8 | |
| 1.5.0 | 6 / 8 | |
| 1.4.2 | 6 / 8 | |
| 1.4.1 | 6 / 8 | |
| 1.4.0 | 6 / 8 | |
| 1.3.3 | 6 / 8 | |
| 1.3.2 | 6 / 8 | |
| 1.2.1 | 7 / 8 |
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.