← Home

@fluidframework/react

npm Repository Homepage

Utilities for integrating content powered by the Fluid Framework into React applications

21
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
dependencies unvetted-dep:quill AI (dependencies): quill is a well-known open-source rich text editor; its use is consistent with this React integration package's stated purpose. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): react-dom is a declared peer/runtime dep for a React integration package; heuristic false positive. ai
phantom-deps phantom-dep:@fluidframework/core-utils AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for transitive re-exports. ai
phantom-deps phantom-dep:@fluidframework/fluid-static AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for transitive re-exports. ai
phantom-deps phantom-dep:@fluidframework/datastore-definitions AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for transitive re-exports. ai

Versions (showing 21 of 21)

Version Deps Published
2.102.0 11 / 28
2.101.1 11 / 28
2.101.0 11 / 28
2.100.1 10 / 27
2.100.0 10 / 27
2.93.0 10 / 27
2.92.0 10 / 27
2.91.0 12 / 27
2.90.0 12 / 26
2.83.0 8 / 25
2.82.0 8 / 25
2.81.1 8 / 25
2.81.0 8 / 25
2.80.0 8 / 25
2.74.0 8 / 25
2.73.0 8 / 24
2.72.0 8 / 24
2.71.0 8 / 24
2.70.0 8 / 24
2.63.0 8 / 24
2.62.0 8 / 24

v2.102.0

1 finding
LOW No provenance attestation provenance

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

v2.101.1

1 finding
LOW No provenance attestation provenance

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

v2.101.0

1 finding
LOW No provenance attestation provenance

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

v2.100.1

1 finding
LOW No provenance attestation provenance

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

v2.100.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.

v2.93.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.

v2.92.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.

v2.91.0

1 finding
LOW No provenance attestation provenance

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

v2.90.0

1 finding
LOW No provenance attestation provenance

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

v2.83.0

1 finding
LOW No provenance attestation provenance

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

v2.82.0

1 finding
LOW No provenance attestation provenance

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

v2.81.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.

v2.81.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.

v2.80.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.

v2.74.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.

v2.73.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.

v2.72.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.

v2.71.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.

v2.70.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.

v2.63.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.

v2.62.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.