@interopio/modals-ui
The [`@interopio/modals-ui`](https://www.npmjs.com/package/@interopio/modals-ui) library provides React components for the modal windows(alerts and dialogs) used in **io.Connect Browser** projects and also enable you to create your own custom modal window
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped UI library; sparse metadata is consistent across the @interopio package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same rationale — internal package, no description is a stable pattern for this org. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages); no other risk signals present for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 2 / 1 | |
| 4.3.0 | 2 / 1 | |
| 1.2.6 | 2 / 2 | |
| 1.2.5 | 2 / 2 | |
| 1.2.4 | 2 / 2 | |
| 1.2.3 | 2 / 2 | |
| 1.2.2 | 2 / 2 | |
| 1.2.1 | 2 / 2 | |
| 1.2.0 | 2 / 2 | |
| 1.1.6 | 2 / 2 | |
| 1.1.5 | 2 / 2 | |
| 1.1.4 | 2 / 2 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.