@fluidframework/protocol-base
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:events_pkg | AI (dependencies): events_pkg is a well-known npm alias for the 'events' polyfill; stable pattern in this package. | 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 | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft FluidFramework sub-package; sparse README is typical for internal protocol libs. | ai | |
| provenance | no-provenance | AI (provenance): Large established Microsoft monorepo; lack of Sigstore provenance is not unusual for this publisher. | 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
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.