@fluidframework/server-services-ordering-zookeeper
Fluid server services zookeeper client implementation
3
Versions
MIT
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): FluidFramework publishes older version branches; dormancy reflects versioned release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:zookeeper | AI (dependencies): zookeeper is the expected native binding for this ZooKeeper client implementation; stable dependency across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft OSS package; sparse README/keywords are typical for internal server-side packages in a monorepo. | 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.