@tamagui/text No license 47 versions

@tamagui/text

npm

47

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

nwienert

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:next	AI (typosquat): Scoped @tamagui/* package; Levenshtein match on 'text' vs 'next' is a stable false positive for this package.	ai	2026/05/20
typosquat	typosquat.levenshtein:nuxt	AI (typosquat): Same false-positive pattern; @tamagui/text is a legitimate monorepo package.	ai	2026/05/20
typosquat	typosquat.levenshtein:jest	AI (typosquat): Same false-positive pattern; @tamagui/text is a legitimate monorepo package.	ai	2026/05/20
phantom-deps	phantom-dep:@tamagui/helpers-tamagui	AI (phantom-deps): Sibling @tamagui/* dep; may be re-exported or used indirectly — stable false positive for this monorepo package.	ai	2026/05/20

Versions (showing 47 of 47)

Version	Deps	Published
2.1.0	3 / 2	2026-05-30
2.0.0	3 / 2	2026-05-23
1.144.4	3 / 2	2026-02-26
1.144.3	3 / 2	2026-01-20
1.144.2	3 / 2	2026-01-16
1.144.1	3 / 2	2026-01-09
1.144.0	3 / 2	2026-01-07
1.143.1	3 / 2	2026-01-05
1.143.0	3 / 2	2026-01-04
1.142.0	3 / 2	2025-12-28
1.141.5	3 / 2	2025-12-18
1.141.4	3 / 2	2025-12-17
1.141.3	3 / 2	2025-12-16
1.141.2	3 / 2	2025-12-15
1.141.1	3 / 2	2025-12-15
1.141.0	3 / 2	2025-12-15
1.140.4	3 / 2	2025-12-14
1.140.3	3 / 2	2025-12-13
1.140.2	3 / 2	2025-12-13
1.140.1	3 / 2	2025-12-13
1.140.0	3 / 2	2025-12-12
1.139.4	3 / 2	2025-12-11
1.139.3	3 / 2	2025-12-10
1.139.2	3 / 2	2025-12-08
1.139.1	3 / 2	2025-12-07
1.139.0	3 / 2	2025-12-07
1.138.6	3 / 2	2025-11-28
1.138.5	3 / 2	2025-11-25
1.138.4	3 / 2	2025-11-25
1.138.3	3 / 2	2025-11-24
1.138.2	3 / 2	2025-11-22
1.138.1	3 / 2	2025-11-21
1.138.0	3 / 2	2025-11-15
1.137.3	3 / 2	2025-11-14
1.137.2	3 / 2	2025-11-13
1.137.1	3 / 2	2025-11-12
1.137.0	3 / 2	2025-11-10
1.136.9	3 / 2	2025-11-09
1.136.8	3 / 2	2025-11-08
1.136.7	3 / 2	2025-11-08
1.136.6	3 / 2	2025-11-08
1.136.5	3 / 2	2025-11-08
1.136.4	3 / 2	2025-11-08
1.136.3	3 / 2	2025-11-08
1.136.2	3 / 2	2025-11-07
1.136.1	3 / 2	2025-11-04
1.136.0	3 / 2	2025-11-04

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.144.4

1 finding

LOW No provenance attestation provenance

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

v1.144.3

2 findings

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

Package name '@tamagui/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.

v1.144.2

1 finding

LOW No provenance attestation provenance

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

v1.144.1

1 finding

LOW No provenance attestation provenance

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

v1.144.0

1 finding

LOW No provenance attestation provenance

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

v1.143.1

1 finding

LOW No provenance attestation provenance

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

v1.143.0

2 findings

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

Package name '@tamagui/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.

v1.142.0

2 findings

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

Package name '@tamagui/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.

v1.141.5

1 finding

LOW No provenance attestation provenance

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

v1.141.4

2 findings

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

Package name '@tamagui/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.

v1.141.3

1 finding

LOW No provenance attestation provenance

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

v1.141.2

2 findings

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

Package name '@tamagui/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.

v1.141.1

2 findings

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

Package name '@tamagui/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.

v1.141.0

2 findings

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

Package name '@tamagui/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.

v1.140.4

2 findings

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

Package name '@tamagui/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.

v1.140.3

1 finding

LOW No provenance attestation provenance

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

v1.140.2

2 findings

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

Package name '@tamagui/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.

v1.140.1

1 finding

LOW No provenance attestation provenance

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

v1.140.0

2 findings

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

Package name '@tamagui/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.

v1.139.4

2 findings

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

Package name '@tamagui/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.

v1.139.3

2 findings

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

Package name '@tamagui/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.

v1.139.2

2 findings

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

Package name '@tamagui/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.

v1.139.1

2 findings

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

Package name '@tamagui/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.

v1.139.0

2 findings

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

Package name '@tamagui/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.

v1.138.6

1 finding

LOW No provenance attestation provenance

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

v1.138.5

1 finding

LOW No provenance attestation provenance

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

v1.138.4

1 finding

LOW No provenance attestation provenance

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

v1.138.3

2 findings

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

Package name '@tamagui/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.

v1.138.2

1 finding

LOW No provenance attestation provenance

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

v1.138.1

1 finding

LOW No provenance attestation provenance

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

v1.138.0

2 findings

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

Package name '@tamagui/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.

v1.137.3

2 findings

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

Package name '@tamagui/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.

v1.137.2

1 finding

LOW No provenance attestation provenance

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

v1.137.1

1 finding

LOW No provenance attestation provenance

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

v1.137.0

1 finding

LOW No provenance attestation provenance

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

v1.136.9

2 findings

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

Package name '@tamagui/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.

v1.136.8

2 findings

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

Package name '@tamagui/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.

v1.136.7

2 findings

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

Package name '@tamagui/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.

v1.136.6

2 findings

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

Package name '@tamagui/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.

v1.136.5

1 finding

LOW No provenance attestation provenance

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

v1.136.4

2 findings

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

Package name '@tamagui/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.

v1.136.3

1 finding

LOW No provenance attestation provenance

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

v1.136.2

2 findings

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

Package name '@tamagui/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.

v1.136.1

1 finding

LOW No provenance attestation provenance

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

v1.136.0

2 findings

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

Package name '@tamagui/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.