@fluidframework/server-services-core
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 trusted. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft FluidFramework monorepo; versioned releases may have irregular cadence across sub-packages without indicating takeover. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only package loaded by convention in TypeScript projects; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/nconf | AI (phantom-deps): Type-only package for nconf; loaded by convention, not directly imported. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft FluidFramework server package; sparse README is a documentation choice, not a spam indicator. | 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.