@fluidframework/server-test-utils
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 OSS monorepo; provenance not yet configured but package is well-established and trustworthy. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft FluidFramework uses automated bot publishing; gap likely reflects versioning cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:@fluidframework/common-utils | AI (dependencies): First-party FluidFramework dependency; stable across versions. | ai | |
| dependencies | unvetted-dep:@fluidframework/protocol-definitions | AI (dependencies): First-party FluidFramework dependency; stable across versions. | ai | |
| dependencies | unvetted-dep:@types/ioredis-mock | AI (dependencies): Well-known types package for ioredis-mock; low risk. | ai | |
| phantom-deps | phantom-dep:@types/ioredis-mock | AI (phantom-deps): @types/ioredis-mock is a type-only dev dependency used by convention in this test-utils package; not a real phantom-dep concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal FluidFramework test-utils package; sparse README and no keywords are expected for monorepo sub-packages. | 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.