@fluentui/react-toast
Toast component for 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, so a manually published version cannot be tied back to a reviewed commit.
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): Microsoft's own CSS-in-JS library, part of the Fluent UI ecosystem. Legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-portal | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion-components-preview | AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-motion | AI (phantom-deps): Common in monorepo packages where deps are declared for version management even if not directly imported in every file. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and no keywords are typical for sub-packages in large monorepos like microsoft/fluentui where docs live on the main site. | ai |
Versions (showing 100 of 125)
| Version | Deps | Published |
|---|---|---|
| 9.8.1 | 13 / 0 | |
| 9.8.0 | 13 / 0 | |
| 9.7.18 | 13 / 0 | |
| 9.7.17 | 13 / 0 | |
| 9.7.16 | 13 / 0 | |
| 9.7.15 | 13 / 0 | |
| 9.7.14 | 13 / 0 | |
| 9.7.13 | 13 / 0 | |
| 9.7.12 | 13 / 0 | |
| 9.7.11 | 13 / 0 | |
| 9.7.10 | 13 / 6 | |
| 9.7.9 | 13 / 6 | |
| 9.7.8 | 13 / 6 | |
| 9.7.7 | 13 / 6 | |
| 9.7.6 | 13 / 6 | |
| 9.7.5 | 13 / 6 | |
| 9.7.4 | 13 / 6 | |
| 9.7.3 | 13 / 6 | |
| 9.7.2 | 13 / 6 | |
| 9.7.1 | 13 / 6 | |
| 9.7.0 | 13 / 6 | |
| 9.6.4 | 13 / 6 | |
| 9.6.3 | 13 / 6 | |
| 9.6.2 | 13 / 6 | |
| 9.6.1 | 13 / 6 | |
| 9.6.0 | 13 / 6 | |
| 9.5.5 | 13 / 6 | |
| 9.5.4 | 13 / 6 | |
| 9.5.3 | 13 / 6 | |
| 9.5.2 | 13 / 6 | |
| 9.5.1 | 13 / 6 | |
| 9.5.0 | 13 / 6 | |
| 9.4.10 | 13 / 6 | |
| 9.4.9 | 13 / 6 | |
| 9.4.8 | 13 / 6 | |
| 9.4.7 | 13 / 6 | |
| 9.4.6 | 13 / 6 | |
| 9.4.5 | 13 / 6 | |
| 9.4.4 | 13 / 6 | |
| 9.4.3 | 13 / 6 | |
| 9.4.2 | 13 / 6 | |
| 9.4.1 | 13 / 6 | |
| 9.4.0 | 13 / 6 | |
| 9.3.65 | 13 / 6 | |
| 9.3.64 | 13 / 6 | |
| 9.3.63 | 13 / 6 | |
| 9.3.62 | 13 / 6 | |
| 9.3.61 | 12 / 6 | |
| 9.3.60 | 12 / 6 | |
| 9.3.59 | 12 / 6 | |
| 9.3.58 | 12 / 7 | |
| 9.3.57 | 12 / 7 | |
| 9.3.56 | 12 / 7 | |
| 9.3.55 | 12 / 6 | |
| 9.3.54 | 12 / 6 | |
| 9.3.53 | 12 / 6 | |
| 9.3.52 | 12 / 6 | |
| 9.3.51 | 12 / 6 | |
| 9.3.50 | 12 / 6 | |
| 9.3.49 | 12 / 6 | |
| 9.3.48 | 12 / 6 | |
| 9.3.47 | 12 / 6 | |
| 9.3.46 | 12 / 6 | |
| 9.3.45 | 12 / 5 | |
| 9.3.44 | 12 / 5 | |
| 9.3.43 | 12 / 5 | |
| 9.3.42 | 12 / 5 | |
| 9.3.41 | 12 / 5 | |
| 9.3.40 | 12 / 5 | |
| 9.3.39 | 12 / 5 | |
| 9.3.38 | 12 / 5 | |
| 9.3.37 | 12 / 5 | |
| 9.3.36 | 12 / 5 | |
| 9.3.35 | 12 / 5 | |
| 9.3.34 | 12 / 5 | |
| 9.3.33 | 12 / 5 | |
| 9.3.32 | 12 / 5 | |
| 9.3.31 | 12 / 5 | |
| 9.3.30 | 12 / 5 | |
| 9.3.29 | 12 / 5 | |
| 9.3.28 | 12 / 5 | |
| 9.3.27 | 12 / 5 | |
| 9.3.26 | 12 / 5 | |
| 9.3.25 | 12 / 5 | |
| 9.3.24 | 12 / 5 | |
| 9.3.23 | 12 / 5 | |
| 9.3.22 | 12 / 5 | |
| 9.3.21 | 12 / 5 | |
| 9.3.20 | 12 / 5 | |
| 9.3.19 | 12 / 5 | |
| 9.3.18 | 12 / 5 | |
| 9.3.17 | 12 / 5 | |
| 9.3.16 | 12 / 5 | |
| 9.3.15 | 12 / 5 | |
| 9.3.14 | 12 / 5 | |
| 9.3.13 | 12 / 5 | |
| 9.3.12 | 12 / 5 | |
| 9.3.11 | 12 / 5 | |
| 9.3.10 | 12 / 5 | |
| 9.3.9 | 12 / 5 |
v9.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.