@fluidframework/container-runtime
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tylerbu/sorted-btree-es6 | AI (dependencies): Known FluidFramework-ecosystem fork of sorted-btree; stable dependency across versions of this package. | ai | |
| phantom-deps | phantom-dep:@tylerbu/sorted-btree-es6 | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Large Microsoft OSS monorepo; provenance not yet adopted; stable across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.102.0 | 17 / 29 | |
| 2.101.1 | 17 / 29 | |
| 2.101.0 | 17 / 29 | |
| 2.100.1 | 17 / 29 | |
| 2.100.0 | 17 / 29 | |
| 2.93.0 | 17 / 29 | |
| 2.92.0 | 17 / 29 |
v2.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.