@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, 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Build tooling change (tsgo) explains missing gitHead; established Microsoft package with trusted bot publisher. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft-maintained monorepo package; gap likely reflects release cadence changes, not account takeover. | ai | |
| 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 51 of 88)
| Version | Deps | Published |
|---|---|---|
| 0.27.5 | 6 / 13 | |
| 0.27.4 | 6 / 13 | |
| 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 | |
| 0.26.2 | 6 / 8 | |
| 0.26.1 | 6 / 8 | |
| 0.26.0 | 6 / 8 | |
| 0.25.5 | 6 / 7 | |
| 0.25.4 | 6 / 7 | |
| 0.25.3 | 6 / 7 | |
| 0.25.2 | 6 / 7 | |
| 0.25.1 | 6 / 7 | |
| 0.25.0 | 6 / 7 | |
| 0.24.0 | 6 / 7 | |
| 0.23.0 | 6 / 7 | |
| 0.22.0 | 6 / 7 | |
| 0.21.1 | 6 / 7 | |
| 0.21.0 | 6 / 7 | |
| 0.9.5 | 5 / 5 | |
| 0.9.4 | 5 / 5 | |
| 0.9.3 | 5 / 5 | |
| 0.9.2 | 5 / 5 | |
| 0.9.1 | 5 / 5 | |
| 0.9.0 | 5 / 5 | |
| 0.8.11 | 5 / 5 | |
| 0.8.10 | 5 / 5 | |
| 0.8.9 | 5 / 5 | |
| 0.8.8 | 5 / 5 | |
| 0.8.7 | 5 / 5 | |
| 0.8.6 | 5 / 5 | |
| 0.8.5 | 5 / 5 | |
| 0.8.4 | 5 / 5 | |
| 0.8.3 | 5 / 5 | |
| 0.8.2 | 5 / 5 | |
| 0.8.1 | 5 / 5 |
v0.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.