@itwin/core-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 — 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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used for class inheritance/prototype chain access in compiled TypeScript — standard pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:inversify | AI (phantom-deps): inversify is a declared runtime dependency used via DI container; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a known implicit runtime dep for TypeScript decorators; stable false positive. | ai | |
| phantom-deps | phantom-dep:@itwin/core-telemetry | AI (phantom-deps): Same-org dep declared in dependencies; may be loaded conditionally. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@itwin/cloud-agnostic-core | AI (phantom-deps): Same-org dep declared in dependencies; may be loaded conditionally. Stable false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used for RPC request deserialization, not obfuscation; stable pattern for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.10.0 | 11 / 43 | |
| 5.9.5 | 11 / 43 | |
| 5.9.4 | 11 / 43 | |
| 5.9.3 | 11 / 43 | |
| 5.9.2 | 11 / 43 | |
| 5.9.1 | 11 / 43 | |
| 5.9.0 | 11 / 43 | |
| 5.8.5 | 11 / 43 | |
| 5.8.4 | 11 / 43 | |
| 5.8.3 | 11 / 43 | |
| 5.8.2 | 11 / 43 | |
| 5.8.1 | 11 / 43 | |
| 5.8.0 | 11 / 43 | |
| 4.11.7 | 16 / 37 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v4.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.