← Home

@fluidframework/server-lambdas

npm Repository Homepage
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.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@fluidframework/common-utils AI (dependencies): First-party FluidFramework monorepo dependency; stable false positive for this package. ai
dependencies unvetted-dep:@fluidframework/protocol-definitions AI (dependencies): First-party FluidFramework monorepo dependency; stable false positive for this package. ai
phantom-deps phantom-dep:async AI (phantom-deps): async is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:nconf AI (phantom-deps): nconf is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Established Microsoft OSS package; sparse README/keywords are normal for internal monorepo packages. ai
phantom-deps phantom-dep:@types/semver AI (phantom-deps): @types/semver declared as runtime dep (unusual but intentional); stable false positive for this package. ai
phantom-deps phantom-dep:buffer AI (phantom-deps): buffer is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
provenance no-provenance AI (provenance): Large Microsoft monorepo; provenance attestation not yet adopted for this package family. ai

Versions (showing 3 of 3)

Version Deps Published
7.0.1 23 / 24
7.0.0 23 / 24
6.0.1 23 / 24

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.