← Home

@fluidframework/server-routerlicious-base

Fluid server base classes for routerlicious

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
publish-pattern dormant-publish AI (publish-pattern): Back-release of older major version (6.x) from a large Microsoft monorepo; not a suspicious account revival. ai
phantom-deps phantom-dep:ioredis AI (phantom-deps): ioredis is a legitimate runtime dep declared in package.json; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:serialize-error AI (phantom-deps): serialize-error is a legitimate runtime dep; phantom-dep heuristic false positive. ai
semgrep semgrep:dynamic-require AI (semgrep): Config-driven plugin loader pattern; stable and documented for this package. ai
bogus-package bogus-package AI (bogus-package): Established Microsoft FluidFramework server package; sparse README is typical for internal server components. ai
provenance no-provenance AI (provenance): Large established Microsoft monorepo package; lack of provenance is consistent across all versions. ai

Versions (showing 3 of 3)

Version Deps Published
7.0.1 34 / 33
7.0.0 34 / 33
6.0.1 34 / 33

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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.