← Home

@fluidframework/server-services-utils

npm Repository Homepage
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.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Microsoft FluidFramework uses automated bot publishing; dormancy between patch releases is expected for this package family. ai
dependencies unvetted-dep:@fluidframework/protocol-definitions AI (dependencies): First-party FluidFramework sibling package; stable across all versions. ai
dependencies unvetted-dep:@fluidframework/server-services-core AI (dependencies): First-party FluidFramework sibling package; stable across all versions. ai
dependencies unvetted-dep:sillyname AI (dependencies): sillyname is a benign random-name generator; stable use in FluidFramework for session/container naming. ai
dependencies unvetted-dep:@fluidframework/server-services-telemetry AI (dependencies): First-party FluidFramework sibling package; stable across all versions. ai
bogus-package bogus-package AI (bogus-package): Legitimate Microsoft OSS package; sparse README is typical for internal utility packages in a monorepo. ai
dependencies unvetted-dep:@fluidframework/server-services-client AI (dependencies): First-party FluidFramework sibling package; stable across all versions. ai

Versions (showing 3 of 3)

Version Deps Published
7.0.1 17 / 24
7.0.0 17 / 24
6.0.1 17 / 24

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.