@tamagui/input — Greenflagged

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
source-diff	obfuscated-file:types/v1/Input.d.ts	AI (source-diff): Long lines are TypeScript union type declarations in .d.ts files, not obfuscated code. Stable false positive for this package.	ai	2026/05/26
source-diff	obfuscated-file:types/v1/Input.native.d.ts	AI (source-diff): Same pattern: TypeScript declaration file with long union types. Stable false positive for this package.	ai	2026/05/26
phantom-deps	phantom-dep:@tamagui/helpers	AI (phantom-deps): Same-org monorepo sibling; stable false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:@tamagui/text	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for bundled/re-exported packages.	ai	2026/05/20
phantom-deps	phantom-dep:@tamagui/helpers-tamagui	AI (phantom-deps): Same-org monorepo sibling; stable false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:@tamagui/font-size	AI (phantom-deps): Same-org monorepo sibling; stable false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:@tamagui/stacks	AI (phantom-deps): Same-org monorepo sibling; stable false positive for this package.	ai	2026/05/20

Versions (showing 47 of 47)

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

3 findings

HIGH New obfuscated file: types/v1/Input.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: types/v1/Input.native.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

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.

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

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.

v1.142.0

1 finding

LOW No provenance attestation provenance

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

v1.141.5

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.

v1.141.4

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.

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

1 finding

LOW No provenance attestation provenance

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

v1.141.1

1 finding

LOW No provenance attestation provenance

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

v1.141.0

1 finding

LOW No provenance attestation provenance

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

v1.140.4

1 finding

LOW No provenance attestation provenance

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

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

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.

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

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.

v1.139.4

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.

v1.139.3

1 finding

LOW No provenance attestation provenance

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

v1.139.2

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.

v1.139.1

1 finding

LOW No provenance attestation provenance

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

v1.139.0

1 finding

LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.138.3

1 finding

LOW No provenance attestation provenance

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

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

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.

v1.137.3

1 finding

LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.136.9

1 finding

LOW No provenance attestation provenance

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

v1.136.8

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.

v1.136.7

1 finding

LOW No provenance attestation provenance

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

v1.136.6

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.136.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.

v1.136.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.