← Home

@fluentui/react-portal

npm Repository Homepage

A utility component that creates portals compatible with Fluent UI

51
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

chrisdholtmiroslavstastnylevithomasonuifabricteamuifrnbotlayershifterjustslonemicrosoft1essopranopillow

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:use-disposable AI (dependencies): Small, established hook dependency used across fluentui packages; not a risk. ai
dependencies unvetted-dep:@fluentui/react-tabster AI (dependencies): Internal @fluentui monorepo dependency from Microsoft. Expected and legitimate for this package. ai
dependencies unvetted-dep:@fluentui/react-utilities AI (dependencies): Internal @fluentui monorepo dependency from Microsoft. Expected and legitimate for this package. ai
dependencies unvetted-dep:@griffel/react AI (dependencies): @griffel/react is a Microsoft-maintained CSS-in-JS library, part of the Fluent UI ecosystem. Expected dependency for this package. ai
phantom-deps phantom-dep:@griffel/react AI (phantom-deps): @griffel/react is used at build/config time in the Fluent UI monorepo (Griffel CSS-in-JS). Not a security concern for this package. ai
provenance no-provenance AI (provenance): Absence of Sigstore provenance is common (~88% of packages lack it). Microsoft's fluentui monorepo is a well-established, trusted source. ai
dependencies unvetted-dep:@fluentui/react-shared-contexts AI (dependencies): Internal @fluentui monorepo dependency from Microsoft. Expected and legitimate for this package. ai

Versions (showing 51 of 148)

View all versions
Version Deps Published
9.8.14 5 / 0
9.8.13 5 / 0
9.8.12 5 / 0
9.8.11 5 / 0
9.8.10 5 / 0
9.8.9 5 / 4
9.8.8 5 / 4
9.8.7 5 / 4
9.8.6 5 / 4
9.8.5 5 / 4
9.8.4 5 / 4
9.8.3 5 / 4
9.8.2 5 / 4
9.8.1 5 / 4
9.8.0 5 / 4
9.7.2 6 / 4
9.7.1 6 / 4
9.7.0 6 / 4
9.6.4 6 / 4
9.6.3 5 / 4
9.6.2 5 / 4
9.6.1 5 / 4
9.6.0 5 / 4
9.5.8 5 / 4
9.5.7 5 / 4
9.5.6 6 / 4
9.5.5 6 / 4
9.5.4 6 / 4
9.5.3 6 / 4
9.5.2 6 / 4
9.5.1 6 / 4
9.5.0 6 / 4
9.4.42 6 / 4
9.4.41 6 / 4
9.4.40 6 / 4
9.4.39 6 / 4
9.4.38 6 / 4
9.4.37 6 / 5
9.4.36 6 / 5
9.4.35 6 / 5
9.4.34 6 / 5
9.4.33 6 / 5
9.4.32 6 / 5
9.4.31 6 / 5
9.4.30 6 / 5
9.4.29 6 / 5
9.4.28 6 / 5
9.4.27 6 / 5
9.4.26 6 / 4
9.4.25 6 / 4
9.4.24 6 / 4

v9.7.2

1 finding
INFO No provenance attestation provenance

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

v9.7.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.

v9.7.0

1 finding
INFO No provenance attestation provenance

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

v9.6.4

1 finding
INFO No provenance attestation provenance

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

v9.5.6

1 finding
INFO No provenance attestation provenance

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

v9.5.5

1 finding
INFO No provenance attestation provenance

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

v9.5.4

1 finding
INFO No provenance attestation provenance

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

v9.5.3

1 finding
INFO No provenance attestation provenance

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

v9.5.2

1 finding
INFO No provenance attestation provenance

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

v9.5.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.

v9.5.0

1 finding
INFO No provenance attestation provenance

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

v9.4.42

1 finding
INFO No provenance attestation provenance

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

v9.4.41

1 finding
INFO No provenance attestation provenance

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

v9.4.40

1 finding
INFO No provenance attestation provenance

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

v9.4.39

1 finding
INFO No provenance attestation provenance

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

v9.4.38

1 finding
INFO No provenance attestation provenance

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

v9.4.37

1 finding
INFO No provenance attestation provenance

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

v9.4.36

1 finding
INFO No provenance attestation provenance

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

v9.4.35

1 finding
INFO No provenance attestation provenance

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

v9.4.34

1 finding
INFO No provenance attestation provenance

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

v9.4.33

1 finding
INFO No provenance attestation provenance

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

v9.4.32

1 finding
INFO No provenance attestation provenance

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

v9.4.31

1 finding
INFO No provenance attestation provenance

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

v9.4.30

1 finding
INFO No provenance attestation provenance

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

v9.4.29

1 finding
INFO No provenance attestation provenance

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

v9.4.28

1 finding
INFO No provenance attestation provenance

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

v9.4.27

1 finding
INFO No provenance attestation provenance

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

v9.4.26

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.

v9.4.25

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.

v9.4.24

1 finding
INFO No provenance attestation provenance

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