@fluentui/react-toast MIT 33 versions

@fluentui/react-toast

npm Repository Homepage

Toast component for Fluent UI

33

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

chrisdholtmiroslavstastnylevithomasonuifabricteamuifrnbotlayershifterjustslonemicrosoft1essopranopillow

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	2026/04/25
dependencies	unvetted-dep:@fluentui/react-aria	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-icons	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-theme	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-motion	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-portal	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/keyboard-keys	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-tabster	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-utilities	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-jsx-runtime	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-shared-contexts	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-motion-components-preview	AI (dependencies): Sibling @fluentui/* package from the microsoft/fluentui monorepo. Legitimate dependency.	ai	2026/04/25
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	2026/04/25
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	2026/04/25

Versions (showing 33 of 33)

Version	Deps	Published
9.8.0	13 / 0	2026-05-27
9.7.18	13 / 0	2026-05-26
9.7.17	13 / 0	2026-04-23
9.7.16	13 / 0	2026-03-30
9.7.15	13 / 0	2026-03-11
9.7.14	13 / 0	2026-03-03
9.7.13	13 / 0	2026-02-25
9.7.12	13 / 0	2026-02-12
9.7.11	13 / 0	2026-01-22
9.7.10	13 / 6	2025-12-17
9.7.9	13 / 6	2025-11-11
9.7.8	13 / 6	2025-11-06
9.7.7	13 / 6	2025-11-06
9.7.6	13 / 6	2025-10-31
9.7.5	13 / 6	2025-10-21
9.7.4	13 / 6	2025-10-08
9.7.3	13 / 6	2025-10-03
9.7.2	13 / 6	2025-10-02
9.7.1	13 / 6	2025-09-08
9.7.0	13 / 6	2025-08-21
9.6.4	13 / 6	2025-08-07
9.6.3	13 / 6	2025-07-30
9.6.2	13 / 6	2025-07-30
9.6.1	13 / 6	2025-07-28
9.6.0	13 / 6	2025-07-17
9.5.5	13 / 6	2025-07-16
9.5.4	13 / 6	2025-07-04
9.5.3	13 / 6	2025-06-27
9.5.2	13 / 6	2025-06-26
9.5.1	13 / 6	2025-06-18
9.5.0	13 / 6	2025-06-12
9.4.10	13 / 6	2025-06-06
9.4.9	13 / 6	2025-05-14

v9.8.0

1 finding

LOW No provenance attestation provenance

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

v9.7.18

1 finding

LOW No provenance attestation provenance

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

v9.7.17

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.

v9.7.16

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.

v9.7.15

1 finding

LOW No provenance attestation provenance

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

v9.7.14

1 finding

LOW No provenance attestation provenance

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

v9.7.13

1 finding

LOW No provenance attestation provenance

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

v9.7.12

1 finding

LOW No provenance attestation provenance

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

v9.7.11

1 finding

LOW No provenance attestation provenance

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

v9.7.10

1 finding

LOW No provenance attestation provenance

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

v9.7.9

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.

v9.7.8

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.

v9.7.7

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.

v9.7.6

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.

v9.7.5

1 finding

LOW No provenance attestation provenance

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

v9.7.4

1 finding

LOW No provenance attestation provenance

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

v9.7.3

1 finding

LOW No provenance attestation provenance

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

v9.7.2

1 finding

LOW No provenance attestation provenance

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

v9.7.1

1 finding

LOW No provenance attestation provenance

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

v9.7.0

1 finding

LOW No provenance attestation provenance

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

v9.6.4

1 finding

LOW No provenance attestation provenance

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

v9.6.3

1 finding

LOW No provenance attestation provenance

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

v9.6.2

1 finding

LOW No provenance attestation provenance

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

v9.6.1

1 finding

LOW No provenance attestation provenance

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

v9.6.0

1 finding

LOW No provenance attestation provenance

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

v9.5.5

1 finding

LOW No provenance attestation provenance

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

v9.5.4

1 finding

LOW No provenance attestation provenance

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

v9.5.3

1 finding

LOW No provenance attestation provenance

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

v9.5.2

1 finding

LOW No provenance attestation provenance

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

v9.5.1

1 finding

LOW No provenance attestation provenance

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

v9.5.0

1 finding

LOW No provenance attestation provenance

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

v9.4.10

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.

v9.4.9

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.