rc-touchable MIT 26 versions

rc-touchable

npm Repository Homepage

React Touchable Component

26

Versions

MIT

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

paranoidjkyiminghe

Keywords

reacttouchablecomponent

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Transfer from yiminghe to paranoidjk occurred in May 2017 within the react-component org. Both are known org contributors; 7+ years of stable publishing under paranoidjk with no incidents.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): paranoidjk is a long-established publisher (first seen 2016) within the react-component org; addition is a legitimate org-level transfer, not a suspicious new actor.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): yiminghe's removal is part of the same 2017 org-level transfer; no evidence of compromise given 7+ years of clean subsequent publishing.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from paranoidjk to yiminghe occurred in 2017; yiminghe is the listed author and a highly trusted publisher with thousands of approved packages. Legitimate transition.	ai	2026/04/24
phantom-deps	phantom-dep:babel-runtime	AI (phantom-deps): babel-runtime is a Babel compile-time helper dependency injected by transpilation, not explicitly imported in source. Standard pattern for Babel-compiled packages.	ai	2026/04/24

Versions (showing 26 of 26)

Version	Deps	Published
1.3.2	1 / 9	2019-03-26
1.3.1	1 / 9	2018-09-25
1.3.0	1 / 9	2018-07-26
1.2.3	1 / 9	2017-07-20
1.2.2	2 / 9	2017-05-16
1.2.1	2 / 9	2017-05-16
1.2.0	2 / 9	2017-05-15
1.1.4	2 / 9	2017-05-05
1.1.3	2 / 9	2017-05-05
1.1.2	2 / 9	2017-05-04
1.1.0	2 / 9	2017-05-04
1.0.13	2 / 9	2017-03-10
1.0.12	2 / 9	2017-03-10
1.0.11	2 / 9	2017-03-07
1.0.10	2 / 9	2017-01-16
1.0.9	2 / 9	2017-01-16
1.0.8	2 / 9	2016-12-13
1.0.7	2 / 9	2016-12-09
1.0.6	3 / 9	2016-12-08
1.0.5	3 / 9	2016-12-08
1.0.4	3 / 9	2016-12-07
1.0.3	3 / 9	2016-12-07
1.0.2	3 / 9	2016-11-30
1.0.1	2 / 9	2016-11-30
1.0.0	2 / 9	2016-11-29
0.0.1	1 / 9	2016-11-29

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: paranoidjk → yiminghe (on 2018-07-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-07-26. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yiminghe → paranoidjk (on 2017-07-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-07-20. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: paranoidjk → yiminghe (on 2017-05-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-16. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yiminghe → paranoidjk (on 2017-05-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-16. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

2 findings

HIGH Publisher changed: paranoidjk → yiminghe (on 2017-05-05) provenance

This version was published by a different npm account than previous versions on 2017-05-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.1.2

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (yiminghe) were replaced by new maintainers (paranoidjk). This is a strong signal of a potential package hijack and requires careful review.

LOW No provenance attestation provenance

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

INFO Publisher changed: yiminghe → paranoidjk (on 2017-05-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-04. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.0.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.