@fluentui-react-native/dependency-profiles
@rnx-kit/align-deps profiles covering packages published from FluentUI-React-Native
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
Versions (showing 100 of 439)
| Version | Deps | Published |
|---|---|---|
| 0.8.72 | 0 / 10 | |
| 0.8.70 | 0 / 10 | |
| 0.8.69 | 0 / 80 | |
| 0.8.68 | 0 / 80 | |
| 0.8.67 | 0 / 80 | |
| 0.8.66 | 0 / 80 | |
| 0.8.65 | 0 / 80 | |
| 0.8.64 | 0 / 80 | |
| 0.8.63 | 0 / 80 | |
| 0.8.62 | 0 / 80 | |
| 0.8.61 | 0 / 80 | |
| 0.8.60 | 0 / 80 | |
| 0.8.59 | 0 / 80 | |
| 0.8.58 | 0 / 80 | |
| 0.8.57 | 0 / 80 | |
| 0.8.56 | 0 / 80 | |
| 0.8.55 | 0 / 80 | |
| 0.8.54 | 0 / 80 | |
| 0.8.53 | 0 / 80 | |
| 0.8.52 | 0 / 80 | |
| 0.8.51 | 0 / 80 | |
| 0.8.50 | 0 / 80 | |
| 0.8.49 | 0 / 80 | |
| 0.8.48 | 0 / 80 | |
| 0.8.47 | 0 / 80 | |
| 0.8.46 | 0 / 80 | |
| 0.8.45 | 0 / 79 | |
| 0.8.44 | 0 / 79 | |
| 0.8.43 | 0 / 79 | |
| 0.8.42 | 0 / 79 | |
| 0.8.41 | 0 / 79 | |
| 0.8.40 | 0 / 79 | |
| 0.8.39 | 0 / 79 | |
| 0.8.38 | 0 / 79 | |
| 0.8.37 | 0 / 79 | |
| 0.8.36 | 0 / 79 | |
| 0.8.35 | 0 / 79 | |
| 0.8.34 | 0 / 79 | |
| 0.8.33 | 0 / 79 | |
| 0.8.32 | 0 / 79 | |
| 0.8.31 | 0 / 79 | |
| 0.8.30 | 0 / 79 | |
| 0.8.29 | 0 / 79 | |
| 0.8.28 | 0 / 79 | |
| 0.8.27 | 0 / 79 | |
| 0.8.26 | 0 / 79 | |
| 0.8.25 | 0 / 79 | |
| 0.8.24 | 0 / 79 | |
| 0.8.23 | 0 / 79 | |
| 0.8.22 | 0 / 79 | |
| 0.8.21 | 0 / 79 | |
| 0.8.20 | 0 / 79 | |
| 0.8.19 | 0 / 79 | |
| 0.8.18 | 0 / 79 | |
| 0.8.17 | 0 / 79 | |
| 0.8.16 | 0 / 79 | |
| 0.8.15 | 0 / 79 | |
| 0.8.14 | 0 / 79 | |
| 0.8.13 | 0 / 79 | |
| 0.8.12 | 0 / 79 | |
| 0.8.11 | 0 / 79 | |
| 0.8.10 | 0 / 79 | |
| 0.8.9 | 0 / 79 | |
| 0.8.8 | 0 / 79 | |
| 0.8.7 | 0 / 79 | |
| 0.8.6 | 0 / 79 | |
| 0.8.5 | 0 / 79 | |
| 0.8.4 | 0 / 79 | |
| 0.8.3 | 0 / 79 | |
| 0.8.2 | 0 / 79 | |
| 0.8.1 | 0 / 79 | |
| 0.8.0 | 0 / 79 | |
| 0.7.36 | 0 / 79 | |
| 0.7.35 | 0 / 79 | |
| 0.7.34 | 0 / 73 | |
| 0.7.33 | 0 / 74 | |
| 0.7.32 | 0 / 74 | |
| 0.7.31 | 0 / 74 | |
| 0.7.30 | 0 / 74 | |
| 0.7.29 | 0 / 74 | |
| 0.7.28 | 0 / 74 | |
| 0.7.27 | 0 / 74 | |
| 0.7.26 | 0 / 74 | |
| 0.7.25 | 0 / 74 | |
| 0.7.24 | 0 / 74 | |
| 0.7.23 | 0 / 74 | |
| 0.7.22 | 0 / 74 | |
| 0.7.21 | 0 / 70 | |
| 0.7.20 | 0 / 70 | |
| 0.7.19 | 0 / 70 | |
| 0.7.18 | 0 / 70 | |
| 0.7.17 | 0 / 70 | |
| 0.7.16 | 0 / 70 | |
| 0.7.15 | 0 / 70 | |
| 0.7.14 | 0 / 70 | |
| 0.7.13 | 0 / 70 | |
| 0.7.12 | 0 / 72 | |
| 0.7.11 | 0 / 72 | |
| 0.7.10 | 0 / 72 | |
| 0.7.9 | 0 / 72 |
v0.8.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.