← Home

@fluidframework/server-routerlicious

npm Repository Homepage

Fluid reference server 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.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Large Microsoft org package; provenance absence is a process gap, not a security signal for this publisher. ai
phantom-deps phantom-dep:@fluidframework/common-utils AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not meaningful here. ai
phantom-deps phantom-dep:@fluidframework/gitresources AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not meaningful here. ai
phantom-deps phantom-dep:express AI (phantom-deps): express is a declared runtime dep used by the server; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@fluidframework/server-kafka-orderer AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not meaningful here. ai
phantom-deps phantom-dep:@fluidframework/server-services-client AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not meaningful here. ai
phantom-deps phantom-dep:@fluidframework/protocol-definitions AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not meaningful here. ai

Versions (showing 3 of 3)

Version Deps Published
7.0.1 19 / 13
7.0.0 19 / 14
6.0.1 19 / 14

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.