@itwin/imodel-browser-react
Components that let the user browse the iModels of a context and select one.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:cjs/mui/index.js | AI (source-diff): Standard Rollup minified bundle output; no obfuscation or malicious patterns present. | ai | |
| source-diff | obfuscated-file:esm/mui/index.js | AI (source-diff): Standard Rollup ESM minified bundle output; no obfuscation or malicious patterns present. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New /mui subpath export legitimately adds many source files; consistent with documented feature addition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Bentley iTwin component library; sparse README/keywords are a style choice, not spam. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 3 / 51 | |
| 4.2.0 | 3 / 48 | |
| 4.1.0 | 3 / 48 | |
| 4.0.0 | 3 / 48 | |
| 3.8.0 | 3 / 48 | |
| 3.7.0 | 3 / 48 | |
| 3.6.0 | 3 / 48 | |
| 3.5.1 | 3 / 48 | |
| 3.5.0 | 3 / 48 |
v4.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.