@fluentui/react-skeleton
Converged v9 Skeleton Component
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): Griffel is Microsoft's official CSS-in-JS library, a known legitimate dependency of all Fluent UI v9 components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): First-party Microsoft Fluent UI v9 package from the same monorepo; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Microsoft Fluent UI v9 package from the same monorepo; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Microsoft Fluent UI v9 package from the same monorepo; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Microsoft Fluent UI v9 package from the same monorepo; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Microsoft Fluent UI v9 package from the same monorepo; legitimate dependency. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-field | AI (phantom-deps): Same-org Fluent UI package; declared but not directly imported is a common pattern in component library monorepos. | ai |
Versions (showing 100 of 127)
| Version | Deps | Published |
|---|---|---|
| 9.7.4 | 7 / 0 | |
| 9.7.3 | 7 / 0 | |
| 9.7.2 | 7 / 0 | |
| 9.7.1 | 7 / 0 | |
| 9.7.0 | 7 / 0 | |
| 9.6.0 | 7 / 0 | |
| 9.5.0 | 7 / 0 | |
| 9.4.15 | 7 / 0 | |
| 9.4.14 | 7 / 0 | |
| 9.4.13 | 7 / 0 | |
| 9.4.12 | 7 / 4 | |
| 9.4.11 | 7 / 4 | |
| 9.4.10 | 7 / 4 | |
| 9.4.9 | 7 / 4 | |
| 9.4.8 | 7 / 4 | |
| 9.4.7 | 7 / 4 | |
| 9.4.6 | 7 / 4 | |
| 9.4.5 | 7 / 4 | |
| 9.4.4 | 7 / 4 | |
| 9.4.3 | 7 / 4 | |
| 9.4.2 | 7 / 4 | |
| 9.4.1 | 7 / 4 | |
| 9.4.0 | 7 / 4 | |
| 9.3.7 | 7 / 4 | |
| 9.3.6 | 7 / 4 | |
| 9.3.5 | 7 / 4 | |
| 9.3.4 | 7 / 4 | |
| 9.3.3 | 7 / 4 | |
| 9.3.2 | 7 / 4 | |
| 9.3.1 | 7 / 4 | |
| 9.3.0 | 7 / 4 | |
| 9.2.9 | 7 / 4 | |
| 9.2.8 | 7 / 4 | |
| 9.2.7 | 7 / 4 | |
| 9.2.6 | 7 / 4 | |
| 9.2.5 | 7 / 4 | |
| 9.2.4 | 7 / 4 | |
| 9.2.3 | 7 / 4 | |
| 9.2.2 | 7 / 4 | |
| 9.2.1 | 7 / 4 | |
| 9.2.0 | 7 / 4 | |
| 9.1.26 | 7 / 4 | |
| 9.1.25 | 7 / 4 | |
| 9.1.24 | 7 / 4 | |
| 9.1.23 | 7 / 4 | |
| 9.1.22 | 7 / 4 | |
| 9.1.21 | 7 / 4 | |
| 9.1.20 | 7 / 4 | |
| 9.1.19 | 7 / 4 | |
| 9.1.18 | 7 / 5 | |
| 9.1.17 | 7 / 5 | |
| 9.1.16 | 7 / 5 | |
| 9.1.15 | 7 / 5 | |
| 9.1.14 | 7 / 5 | |
| 9.1.13 | 7 / 5 | |
| 9.1.12 | 7 / 5 | |
| 9.1.11 | 7 / 5 | |
| 9.1.10 | 7 / 5 | |
| 9.1.9 | 7 / 5 | |
| 9.1.8 | 7 / 5 | |
| 9.1.7 | 7 / 5 | |
| 9.1.6 | 7 / 5 | |
| 9.1.5 | 7 / 5 | |
| 9.1.4 | 7 / 5 | |
| 9.1.3 | 7 / 5 | |
| 9.1.2 | 7 / 5 | |
| 9.1.1 | 7 / 5 | |
| 9.1.0 | 7 / 5 | |
| 9.0.59 | 7 / 5 | |
| 9.0.58 | 7 / 5 | |
| 9.0.57 | 7 / 5 | |
| 9.0.56 | 7 / 5 | |
| 9.0.55 | 7 / 5 | |
| 9.0.54 | 7 / 5 | |
| 9.0.53 | 7 / 5 | |
| 9.0.52 | 7 / 5 | |
| 9.0.51 | 7 / 5 | |
| 9.0.50 | 7 / 5 | |
| 9.0.49 | 7 / 5 | |
| 9.0.48 | 7 / 5 | |
| 9.0.47 | 7 / 5 | |
| 9.0.46 | 7 / 5 | |
| 9.0.45 | 7 / 5 | |
| 9.0.44 | 7 / 5 | |
| 9.0.43 | 7 / 5 | |
| 9.0.42 | 7 / 5 | |
| 9.0.41 | 7 / 5 | |
| 9.0.40 | 7 / 5 | |
| 9.0.39 | 7 / 5 | |
| 9.0.38 | 7 / 5 | |
| 9.0.37 | 7 / 5 | |
| 9.0.36 | 7 / 5 | |
| 9.0.35 | 7 / 5 | |
| 9.0.34 | 7 / 5 | |
| 9.0.33 | 7 / 5 | |
| 9.0.32 | 7 / 5 | |
| 9.0.31 | 7 / 5 | |
| 9.0.30 | 7 / 5 | |
| 9.0.29 | 7 / 5 | |
| 9.0.27 | 7 / 5 |
v9.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.