@fluidframework/server-services-telemetry
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
ms-fluid-bot
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Microsoft package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft org package with 180 versions; versioned patch releases after gaps are normal for this monorepo. | ai | |
| dependencies | unvetted-dep:@fluidframework/common-utils | AI (dependencies): Same org scope (@fluidframework); stable internal dependency across many versions. | ai | |
| phantom-deps | phantom-dep:@fluidframework/common-utils | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for intra-monorepo packages. | ai | |
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): Referenced in config files for browser bundling; stable false positive for this package. | ai |
v7.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.