@tecsinapse/react-native-kit
React Native components library
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-international-phone | AI (phantom-deps): Declared as runtime dep for phone input component; phantom-dep heuristic fires because it's referenced in config/re-exports rather than direct imports. | ai | |
| dependencies | unvetted-dep:@emotion/native | AI (dependencies): @emotion/native is a well-known, widely-used styling library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived org package; lack of provenance is consistent across all prior versions, not a new risk. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 6 / 1 | |
| 4.1.0 | 6 / 1 | |
| 4.0.4 | 4 / 1 | |
| 4.0.2 | 4 / 1 | |
| 4.0.1 | 4 / 1 | |
| 4.0.0 | 4 / 1 | |
| 3.5.17 | 4 / 1 | |
| 3.5.16 | 4 / 1 | |
| 3.5.15 | 4 / 1 |
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.