@fluentui/react-motion-components-preview
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 |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.15.6 | 3 / 0 | |
| 0.15.5 | 3 / 0 | |
| 0.15.4 | 3 / 0 | |
| 0.15.3 | 3 / 0 | |
| 0.15.2 | 3 / 0 | |
| 0.15.1 | 3 / 0 | |
| 0.15.0 | 3 / 0 | |
| 0.14.2 | 3 / 4 | |
| 0.14.1 | 3 / 4 | |
| 0.14.0 | 3 / 4 | |
| 0.13.0 | 2 / 4 | |
| 0.12.0 | 2 / 4 | |
| 0.11.1 | 2 / 4 | |
| 0.11.0 | 2 / 4 | |
| 0.10.1 | 2 / 4 | |
| 0.10.0 | 2 / 4 | |
| 0.9.0 | 2 / 4 | |
| 0.8.2 | 2 / 4 | |
| 0.8.1 | 2 / 4 | |
| 0.8.0 | 2 / 4 | |
| 0.7.0 | 2 / 4 | |
| 0.6.2 | 2 / 4 | |
| 0.6.1 | 2 / 4 | |
| 0.6.0 | 2 / 4 | |
| 0.5.1 | 2 / 4 | |
| 0.5.0 | 2 / 4 | |
| 0.4.9 | 2 / 4 | |
| 0.4.8 | 2 / 4 | |
| 0.4.7 | 2 / 4 | |
| 0.4.6 | 2 / 4 | |
| 0.4.5 | 2 / 4 | |
| 0.4.4 | 2 / 4 | |
| 0.4.3 | 2 / 4 | |
| 0.4.2 | 2 / 4 | |
| 0.4.1 | 2 / 4 | |
| 0.4.0 | 2 / 4 | |
| 0.3.2 | 2 / 4 | |
| 0.3.1 | 2 / 4 | |
| 0.3.0 | 2 / 4 | |
| 0.2.0 | 2 / 5 | |
| 0.1.4 | 2 / 5 | |
| 0.1.3 | 2 / 5 | |
| 0.1.2 | 2 / 5 | |
| 0.1.1 | 2 / 5 | |
| 0.1.0 | 2 / 5 |
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.