@itwin/editor-backend
iTwin.js editor backend
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Bentley/iTwin publisher; lack of Sigstore provenance is consistent across all their packages. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 5.11.3 | 1 / 9 | |
| 5.11.2 | 1 / 9 | |
| 5.11.1 | 1 / 9 | |
| 5.11.0 | 1 / 9 | |
| 5.10.3 | 1 / 9 | |
| 5.10.2 | 1 / 9 | |
| 5.10.1 | 1 / 9 | |
| 5.10.0 | 1 / 9 | |
| 5.9.5 | 1 / 9 | |
| 5.9.4 | 1 / 9 | |
| 5.9.3 | 1 / 9 | |
| 5.9.2 | 1 / 9 | |
| 5.9.1 | 1 / 9 | |
| 5.9.0 | 1 / 9 | |
| 5.8.5 | 1 / 9 | |
| 5.8.4 | 1 / 9 | |
| 5.8.3 | 1 / 9 | |
| 5.8.2 | 1 / 9 | |
| 5.8.1 | 1 / 9 | |
| 5.8.0 | 1 / 9 | |
| 5.7.3 | 1 / 9 | |
| 5.7.2 | 1 / 9 | |
| 5.7.1 | 1 / 9 | |
| 5.7.0 | 1 / 9 | |
| 5.6.3 | 1 / 9 | |
| 5.6.2 | 1 / 9 | |
| 5.6.1 | 1 / 9 | |
| 5.6.0 | 1 / 9 | |
| 5.5.2 | 1 / 9 | |
| 5.5.1 | 1 / 9 | |
| 5.5.0 | 1 / 9 | |
| 5.4.2 | 1 / 9 | |
| 5.4.1 | 1 / 9 | |
| 5.4.0 | 1 / 9 | |
| 5.3.4 | 1 / 9 | |
| 5.3.3 | 1 / 9 | |
| 5.3.2 | 1 / 9 | |
| 5.3.1 | 1 / 9 | |
| 5.3.0 | 1 / 9 | |
| 5.2.6 | 1 / 9 | |
| 5.2.5 | 1 / 9 | |
| 5.2.4 | 1 / 9 | |
| 5.2.3 | 1 / 9 | |
| 5.2.2 | 1 / 9 | |
| 5.2.1 | 1 / 9 | |
| 5.2.0 | 1 / 9 | |
| 5.1.9 | 1 / 9 | |
| 5.1.8 | 1 / 9 | |
| 5.1.7 | 1 / 9 | |
| 5.1.6 | 1 / 9 | |
| 5.1.5 | 1 / 9 |
v5.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.