fluid-framework
The main entry point into Fluid Framework public packages
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/map | AI (dependencies): First-party sibling package co-released at matching version; stable pattern across all fluid-framework releases. | ai | |
| dependencies | unvetted-dep:@fluidframework/tree | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/sequence | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/core-utils | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/fluid-static | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/runtime-utils | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/core-interfaces | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/container-loader | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/driver-definitions | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/shared-object-base | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| dependencies | unvetted-dep:@fluidframework/container-definitions | AI (dependencies): First-party sibling package co-released at matching version. | ai | |
| provenance | no-provenance | AI (provenance): Large Microsoft monorepo; lack of Sigstore provenance is consistent across all fluid-framework versions. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 2.102.0 | 11 / 15 | |
| 2.101.1 | 11 / 15 | |
| 2.101.0 | 11 / 15 | |
| 2.100.1 | 11 / 15 | |
| 2.100.0 | 11 / 15 | |
| 2.93.0 | 11 / 15 | |
| 2.92.0 | 11 / 14 | |
| 2.91.0 | 11 / 14 | |
| 2.90.0 | 11 / 14 | |
| 2.83.0 | 11 / 14 | |
| 2.82.0 | 11 / 14 | |
| 2.81.1 | 11 / 14 | |
| 2.81.0 | 11 / 14 | |
| 2.80.0 | 11 / 14 | |
| 2.74.0 | 11 / 14 | |
| 2.73.0 | 11 / 13 | |
| 2.72.0 | 11 / 13 | |
| 2.71.0 | 11 / 13 | |
| 2.70.0 | 11 / 13 | |
| 2.63.0 | 11 / 13 | |
| 2.62.0 | 11 / 13 | |
| 2.61.0 | 11 / 13 | |
| 2.60.0 | 11 / 13 | |
| 2.53.1 | 11 / 13 | |
| 2.53.0 | 11 / 13 | |
| 2.52.0 | 11 / 13 | |
| 2.51.0 | 11 / 13 | |
| 2.50.0 | 11 / 13 | |
| 2.43.0 | 11 / 13 | |
| 2.42.0 | 11 / 13 | |
| 2.41.0 | 11 / 13 | |
| 2.40.0 | 11 / 13 | |
| 2.33.2 | 11 / 13 | |
| 2.33.1 | 11 / 13 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.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.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.