@fluentui/react-motion-components-preview No license 25 versions

@fluentui/react-motion-components-preview

npm Repository Homepage

25

Versions

—

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
publish-pattern	new-deps-added	AI (publish-pattern): @fluentui/react-utilities is a first-party Microsoft Fluent UI package from the same monorepo; adding it as a dependency is expected and not a supply-chain risk.	ai	2026/04/27
dependencies	unvetted-dep:@fluentui/react-motion	AI (dependencies): Internal sibling package from the Microsoft Fluent UI monorepo; wildcard constraint is standard monorepo practice, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-utilities	AI (dependencies): Internal sibling package from the Microsoft Fluent UI monorepo; wildcard constraint is standard monorepo practice, not a security concern.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): Preview package in a large Microsoft monorepo; minimal README and no keywords are quality issues, not security signals.	ai	2026/04/25

Versions (showing 25 of 25)

Version	Deps	Published
0.15.5	3 / 0	2026-05-26
0.15.4	3 / 0	2026-04-23
0.15.3	3 / 0	2026-03-30
0.15.2	3 / 0	2026-03-03
0.15.1	3 / 0	2026-02-25
0.15.0	3 / 0	2026-01-22
0.14.2	3 / 4	2025-12-17
0.14.1	3 / 4	2025-11-11
0.14.0	3 / 4	2025-11-06
0.13.0	2 / 4	2025-11-06
0.12.0	2 / 4	2025-10-31
0.11.1	2 / 4	2025-10-08
0.11.0	2 / 4	2025-10-03
0.10.1	2 / 4	2025-10-02
0.10.0	2 / 4	2025-09-08
0.9.0	2 / 4	2025-08-21
0.8.2	2 / 4	2025-08-07
0.8.1	2 / 4	2025-07-30
0.8.0	2 / 4	2025-07-28
0.7.0	2 / 4	2025-07-16
0.6.2	2 / 4	2025-06-26
0.6.1	2 / 4	2025-06-18
0.6.0	2 / 4	2025-06-12
0.5.1	2 / 4	2025-06-06
0.5.0	2 / 4	2025-05-14

v0.15.5

1 finding

LOW No provenance attestation provenance

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

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

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

v0.15.2

1 finding

LOW No provenance attestation provenance

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

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.2

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.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.

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.1

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.

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