@fluidframework/merge-tree
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Large Microsoft monorepo package; provenance not yet adopted across the FluidFramework release pipeline. | ai | |
| dependencies | unvetted-dep:@fluidframework/core-utils | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@fluid-internal/client-utils | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@fluidframework/core-interfaces | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@fluidframework/driver-definitions | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@fluidframework/shared-object-base | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@fluidframework/container-definitions | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency pattern. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.112.0 | 10 / 27 | |
| 2.111.0 | 10 / 27 | |
| 2.110.0 | 10 / 27 | |
| 2.103.0 | 10 / 27 | |
| 2.102.0 | 10 / 27 | |
| 2.101.1 | 10 / 27 | |
| 2.101.0 | 10 / 27 | |
| 2.100.1 | 10 / 27 | |
| 2.100.0 | 10 / 27 | |
| 2.93.0 | 10 / 27 | |
| 2.92.0 | 10 / 27 | |
| 2.91.0 | 10 / 27 | |
| 2.90.0 | 10 / 27 | |
| 2.83.0 | 10 / 27 | |
| 2.82.0 | 10 / 27 | |
| 2.81.1 | 10 / 27 | |
| 2.81.0 | 10 / 27 | |
| 2.80.0 | 10 / 27 | |
| 2.74.0 | 10 / 27 | |
| 2.73.0 | 10 / 26 | |
| 2.72.0 | 10 / 26 | |
| 2.71.0 | 10 / 26 |
v2.112.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.111.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.110.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.83.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.82.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.80.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.74.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.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.71.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.