@fluidframework/azure-client
A tool to enable creation and loading of Fluid containers using the Azure Fluid Relay service
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:@fluidframework/driver-utils | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@fluidframework/fluid-static | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@fluidframework/core-interfaces | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@fluidframework/telemetry-utils | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@fluidframework/container-loader | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@fluidframework/driver-definitions | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@fluidframework/routerlicious-driver | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@fluidframework/container-definitions | AI (dependencies): Sibling FluidFramework monorepo package; version-locked to same release. | ai | |
| provenance | no-provenance | AI (provenance): Large Microsoft OSS monorepo; absence of Sigstore provenance is common and not a risk indicator here. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 2.102.0 | 9 / 26 | |
| 2.101.1 | 8 / 26 | |
| 2.101.0 | 8 / 26 | |
| 2.100.1 | 8 / 26 | |
| 2.100.0 | 8 / 26 | |
| 2.93.0 | 8 / 26 | |
| 2.92.0 | 8 / 26 | |
| 2.91.0 | 8 / 26 | |
| 2.90.0 | 8 / 26 | |
| 2.83.0 | 8 / 26 | |
| 2.82.0 | 8 / 26 | |
| 2.81.1 | 8 / 26 | |
| 2.81.0 | 8 / 26 | |
| 2.80.0 | 8 / 26 | |
| 2.74.0 | 8 / 26 | |
| 2.73.0 | 8 / 25 | |
| 2.72.0 | 8 / 25 | |
| 2.71.0 | 8 / 25 | |
| 2.70.0 | 8 / 25 | |
| 2.63.0 | 8 / 25 | |
| 2.62.0 | 8 / 25 | |
| 2.61.0 | 8 / 25 | |
| 2.60.0 | 8 / 25 | |
| 2.53.1 | 8 / 25 | |
| 2.53.0 | 8 / 25 | |
| 2.52.0 | 8 / 25 | |
| 2.51.0 | 8 / 25 | |
| 2.50.0 | 8 / 26 | |
| 2.43.0 | 8 / 26 | |
| 2.42.0 | 8 / 26 | |
| 2.41.0 | 8 / 25 | |
| 2.40.0 | 9 / 25 | |
| 2.33.2 | 9 / 25 | |
| 2.33.1 | 9 / 25 |
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.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.
v2.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.53.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.2
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.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.