@fluidframework/server-kafka-orderer
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): Large Microsoft monorepo package; provenance absence is consistent across all FluidFramework packages. | ai | |
| dependencies | unvetted-dep:@fluidframework/protocol-definitions | AI (dependencies): First-party Microsoft FluidFramework dependency; stable false positive for this package family. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft publishes multiple version lines; back-releases of older minor versions are expected for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft FluidFramework monorepo package; sparse README and no keywords are expected for internal server components. | 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.