@fluentui/react-portal
A utility component that creates portals compatible with Fluent UI
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | |
| 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:@fluentui/react-shared-contexts | AI (dependencies): Internal @fluentui monorepo dependency from Microsoft. Expected and legitimate 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 |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 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.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 |
v9.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.