@itwin/core-electron
iTwin.js ElectronHost and ElectronApp
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@openid/appauth | AI (dependencies): @openid/appauth is the official OpenID Foundation AppAuth library; stable and well-known, not a risk for this package. | ai | |
| phantom-deps | phantom-dep:open | AI (phantom-deps): open is a declared runtime dep used indirectly via Electron host; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:username | AI (phantom-deps): username is a declared runtime dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@openid/appauth | AI (phantom-deps): appauth is a declared runtime dep used indirectly via auth flow; stable false positive for this package. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 5.10.0 | 3 / 21 | |
| 5.9.5 | 3 / 21 | |
| 5.9.4 | 3 / 21 | |
| 5.9.3 | 3 / 21 | |
| 5.9.2 | 3 / 21 | |
| 5.9.1 | 3 / 21 | |
| 5.9.0 | 3 / 21 | |
| 5.8.5 | 3 / 21 | |
| 5.8.4 | 3 / 21 | |
| 5.8.3 | 3 / 21 | |
| 5.8.2 | 3 / 21 | |
| 5.8.1 | 3 / 21 | |
| 5.8.0 | 3 / 21 | |
| 5.7.3 | 3 / 21 | |
| 5.7.2 | 3 / 21 | |
| 5.7.1 | 3 / 21 | |
| 5.7.0 | 3 / 21 | |
| 5.6.3 | 3 / 21 | |
| 5.6.2 | 3 / 21 | |
| 5.6.1 | 3 / 21 | |
| 5.6.0 | 3 / 21 | |
| 5.5.2 | 3 / 21 | |
| 5.5.1 | 3 / 21 | |
| 5.5.0 | 3 / 21 | |
| 5.4.2 | 3 / 21 | |
| 5.4.1 | 3 / 21 | |
| 5.4.0 | 3 / 21 | |
| 5.3.4 | 3 / 21 | |
| 5.3.3 | 3 / 21 | |
| 5.3.2 | 3 / 21 | |
| 5.3.1 | 3 / 21 | |
| 5.3.0 | 3 / 21 | |
| 5.2.6 | 3 / 21 | |
| 5.2.5 | 3 / 21 | |
| 5.2.4 | 3 / 21 | |
| 5.2.3 | 3 / 21 | |
| 5.2.2 | 3 / 21 | |
| 5.2.1 | 3 / 21 | |
| 5.2.0 | 3 / 21 | |
| 5.1.9 | 3 / 21 | |
| 5.1.8 | 3 / 21 | |
| 5.1.7 | 3 / 21 | |
| 5.1.6 | 3 / 21 | |
| 5.1.5 | 3 / 21 | |
| 5.1.4 | 3 / 21 | |
| 5.1.3 | 3 / 21 | |
| 5.1.2 | 3 / 21 | |
| 5.1.1 | 3 / 21 | |
| 5.1.0 | 3 / 21 | |
| 5.0.5 | 3 / 21 | |
| 5.0.4 | 3 / 21 | |
| 5.0.3 | 3 / 21 | |
| 5.0.2 | 3 / 21 | |
| 5.0.1 | 3 / 21 | |
| 5.0.0 | 3 / 21 | |
| 4.11.7 | 3 / 20 |
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.