@fluidframework/matrix
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Official Microsoft FluidFramework package published by ms-fluid-bot; dormancy likely reflects release cadence, not account takeover. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit dependency in TypeScript builds; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@fluidframework/merge-tree | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluid-internal/client-utils | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluidframework/core-interfaces | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency. | ai | |
| dependencies | unvetted-dep:@tiny-calc/nano | AI (dependencies): Known stable alpha dependency used by FluidFramework matrix package across many versions. | ai | |
| dependencies | unvetted-dep:@fluidframework/shared-object-base | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Large Microsoft monorepo; lack of Sigstore provenance is consistent across all FluidFramework releases. | ai | |
| dependencies | unvetted-dep:@fluidframework/driver-definitions | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluidframework/core-utils | AI (dependencies): Sibling FluidFramework monorepo package at matching version; expected dependency. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.101.0 | 13 / 31 | |
| 2.100.0 | 13 / 31 | |
| 2.93.0 | 13 / 31 | |
| 2.92.0 | 14 / 31 | |
| 2.83.0 | 14 / 31 | |
| 2.81.1 | 14 / 31 | |
| 2.81.0 | 14 / 31 | |
| 2.80.0 | 14 / 31 | |
| 2.74.0 | 14 / 31 | |
| 2.73.0 | 14 / 30 | |
| 2.72.0 | 14 / 30 | |
| 2.53.1 | 14 / 30 | |
| 2.52.0 | 14 / 30 | |
| 2.51.0 | 14 / 30 | |
| 2.50.0 | 14 / 30 | |
| 2.42.0 | 14 / 30 | |
| 2.41.0 | 14 / 30 | |
| 2.40.0 | 14 / 30 |
v2.101.0
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.83.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.81.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.
v2.81.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.80.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.74.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.73.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.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.53.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.
v2.52.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.51.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.50.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.42.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.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.