← Home

@fluentui-react-native/text

npm Repository Homepage

A cross-platform Text component using the Fluent Design System

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
typosquat typosquat.levenshtein:next AI (typosquat): Scoped package @fluentui-react-native/text is a legitimate Microsoft FluentUI component; Levenshtein match against 'next' is a false positive for this well-established monorepo package. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped package @fluentui-react-native/text is a legitimate Microsoft FluentUI component; Levenshtein match against 'nuxt' is a false positive. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped package @fluentui-react-native/text is a legitimate Microsoft FluentUI component; Levenshtein match against 'jest' is a false positive. ai

Versions (showing 18 of 18)

Version Deps Published
0.25.3 6 / 20
0.25.1 6 / 20
0.25.0 6 / 20
0.24.21 6 / 15
0.24.20 6 / 15
0.24.19 6 / 15
0.24.18 6 / 15
0.24.17 6 / 15
0.24.16 6 / 15
0.24.15 7 / 11
0.24.14 7 / 11
0.24.13 7 / 11
0.24.12 7 / 11
0.24.11 7 / 11
0.24.10 7 / 11
0.24.9 7 / 11
0.24.8 7 / 11
0.24.7 7 / 9

v0.25.3

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@fluentui-react-native/text' is 1 edit(s) away from popular package 'next'.

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.25.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.25.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.24.17

1 finding
LOW No provenance attestation provenance

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