← Home

@fluentui-react-native/win32-theme

npm Repository Homepage

Win32 office theme that works with the theming native module

18
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jasonvmorseacoatesuifrnbothansenyy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 Microsoft monorepo package; sparse README and no keywords are expected for this type of library component, not spam indicators. ai
dependencies unvetted-dep:@fluentui-react-native/theme-tokens AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency. ai
dependencies unvetted-dep:@fluentui-react-native/default-theme AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency. ai
dependencies unvetted-dep:@fluentui-react-native/design-tokens-win32 AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency. ai

Versions (showing 18 of 18)

Version Deps Published
0.39.3 7 / 17
0.39.1 7 / 17
0.39.0 7 / 17
0.38.0 7 / 13
0.37.1 7 / 13
0.37.0 7 / 13
0.36.0 7 / 13
0.35.0 7 / 13
0.34.15 7 / 13
0.34.14 8 / 11
0.34.13 8 / 11
0.34.12 8 / 11
0.34.11 8 / 11
0.34.10 8 / 11
0.34.9 8 / 11
0.34.8 8 / 11
0.34.7 8 / 11
0.34.6 8 / 9

v0.39.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.39.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.39.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.37.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.34.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.