@fluentui-react-native/default-theme
Typing only package for fluentui-react-native theme types
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Microsoft monorepo package; provenance not yet adopted by this publisher across the ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package from Microsoft's FluentUI React Native project; short README and no keywords are expected for this type of library component. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/theme-tokens | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo; consistently co-versioned and benign. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.27.3 | 6 / 17 | |
| 0.27.1 | 6 / 17 | |
| 0.27.0 | 6 / 17 | |
| 0.26.17 | 6 / 13 | |
| 0.26.16 | 6 / 13 | |
| 0.26.15 | 6 / 13 | |
| 0.26.14 | 6 / 13 | |
| 0.26.13 | 6 / 13 | |
| 0.26.12 | 6 / 13 | |
| 0.26.11 | 6 / 11 | |
| 0.26.10 | 6 / 11 | |
| 0.26.9 | 6 / 11 | |
| 0.26.8 | 6 / 11 | |
| 0.26.7 | 6 / 11 | |
| 0.26.6 | 6 / 11 | |
| 0.26.5 | 6 / 11 | |
| 0.26.4 | 6 / 11 | |
| 0.26.3 | 6 / 9 |
v0.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.