@fluidframework/fluid-telemetry
Customer facing Fluid telemetry types and classes for both producing and consuming said telemetry
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): ms-fluid-bot is a trusted Microsoft automation account; release cadence gaps are expected for this SDK. | ai | |
| dependencies | unvetted-dep:@microsoft/applicationinsights-web | AI (dependencies): Microsoft's official Application Insights SDK; expected runtime dep for a telemetry package from FluidFramework. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft OSS project; provenance not yet adopted across the FluidFramework publish pipeline. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.101.0 | 5 / 25 | |
| 2.100.0 | 5 / 25 | |
| 2.93.0 | 5 / 25 | |
| 2.92.0 | 5 / 25 | |
| 2.82.0 | 5 / 25 | |
| 2.81.0 | 5 / 25 | |
| 2.74.0 | 5 / 25 | |
| 2.70.0 | 5 / 24 | |
| 2.63.0 | 5 / 24 | |
| 2.62.0 | 5 / 24 | |
| 2.61.0 | 5 / 24 | |
| 2.60.0 | 5 / 24 | |
| 2.53.1 | 5 / 24 | |
| 2.53.0 | 5 / 24 | |
| 2.51.0 | 5 / 24 | |
| 2.50.0 | 5 / 25 | |
| 2.43.0 | 5 / 25 | |
| 2.42.0 | 5 / 25 | |
| 2.33.2 | 5 / 25 | |
| 2.33.1 | 5 / 25 |
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.82.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.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.70.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.63.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.62.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.61.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.60.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.53.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.43.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.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.