@fluentui/react-motion MIT 22 versions

@fluentui/react-motion

npm Repository Homepage

A package with utilities & motion definitions using Web Animations API

22

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:@fluentui/react-utilities	AI (dependencies): Sibling package in the same Microsoft Fluent UI monorepo; published by the same team and not a third-party risk.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-shared-contexts	AI (dependencies): Sibling package in the same Microsoft Fluent UI monorepo; published by the same team and not a third-party risk.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): Short README and missing keywords are typical for monorepo sub-packages; not indicative of spam or low-value content for this established Microsoft package.	ai	2026/04/25

Versions (showing 22 of 22)

Version	Deps	Published
9.16.0	3 / 0	2026-05-26
9.15.0	3 / 0	2026-04-23
9.14.0	3 / 0	2026-03-30
9.13.0	3 / 0	2026-03-03
9.12.0	3 / 0	2026-02-25
9.11.6	3 / 0	2026-01-22
9.11.5	3 / 5	2025-12-17
9.11.4	3 / 5	2025-11-11
9.11.3	3 / 5	2025-11-06
9.11.2	3 / 5	2025-10-31
9.11.1	3 / 5	2025-10-08
9.11.0	3 / 5	2025-10-02
9.10.4	3 / 5	2025-09-08
9.10.3	3 / 5	2025-08-21
9.10.2	3 / 5	2025-08-07
9.10.1	3 / 5	2025-07-30
9.10.0	3 / 5	2025-07-28
9.9.0	3 / 5	2025-06-26
9.8.1	3 / 5	2025-06-18
9.8.0	3 / 5	2025-06-12
9.7.4	3 / 5	2025-06-06
9.7.3	3 / 5	2025-05-14

v9.16.0

1 finding

LOW No provenance attestation provenance

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

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

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

v9.13.0

1 finding

LOW No provenance attestation provenance

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

v9.12.0

1 finding

LOW No provenance attestation provenance

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

v9.11.6

1 finding

LOW No provenance attestation provenance

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

v9.11.5

1 finding

LOW No provenance attestation provenance

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

v9.11.4

1 finding

LOW No provenance attestation provenance

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

v9.11.3

1 finding

LOW No provenance attestation provenance

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

v9.11.2

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

1 finding

LOW No provenance attestation provenance

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

v9.11.0

1 finding

LOW No provenance attestation provenance

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

v9.10.4

1 finding

LOW No provenance attestation provenance

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

v9.10.3

1 finding

LOW No provenance attestation provenance

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

v9.10.2

1 finding

LOW No provenance attestation provenance

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

v9.10.1

1 finding

LOW No provenance attestation provenance

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

v9.10.0

1 finding

LOW No provenance attestation provenance

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

v9.9.0

1 finding

LOW No provenance attestation provenance

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

v9.8.1

1 finding

LOW No provenance attestation provenance

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

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

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

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.