@regulaforensics/idv-gui
Regula framework agnostic web components to work with gui idv
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-device-detect | AI (dependencies): react-device-detect is a well-known, widely-used device detection library; its use in a GUI component library is expected and benign. | ai | |
| phantom-deps | phantom-dep:qrcode.react | AI (phantom-deps): Declared dependency likely bundled via Vite into the dist output; phantom-dep pattern is expected for this type of component library. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Declared dependency likely bundled via Vite into the dist output; phantom-dep pattern is expected for this type of component library. | ai | |
| phantom-deps | phantom-dep:react-device-detect | AI (phantom-deps): Declared dependency likely bundled via Vite into the dist output; phantom-dep pattern is expected for this type of component library. | ai | |
| provenance | no-provenance | AI (provenance): Regula Forensics is an established publisher; lack of Sigstore provenance is common (~88% of packages) and not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.6.367 | 4 / 0 | |
| 3.4.316 | 4 / 0 | |
| 3.3.308 | 3 / 0 | |
| 3.2.290 | 3 / 0 | |
| 3.2.283 | 3 / 0 | |
| 3.1.239 | 3 / 0 | |
| 3.1.231 | 3 / 0 |
v3.4.316
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.231
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.