← Home

rmc-feedback

npm Repository Homepage

:active pseudo-class with react for mobile

9
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

kgtongparanoidjksilentcloudwarmhug

Keywords

reactreact-componenttouch feeedbackrc-swipeoutactive pseudo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from paranoidjk to kgtong occurred in 2018 within the react-component org; kgtong is a long-standing trusted publisher. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer additions are normal team rotation within the Ant Design react-component ecosystem. ai
bogus-package bogus-package AI (bogus-package): Spam-publisher flag is FP for react-component org members; 42-byte entry point is a normal barrel re-export. ai

Versions (showing 9 of 9)

Version Deps Published
2.0.0 2 / 9
1.0.4 2 / 9
1.0.3 2 / 9
1.0.2 2 / 9
1.0.1 2 / 9
1.0.0 2 / 9
0.0.3 2 / 9
0.0.2 2 / 9
0.0.1 2 / 9

v2.0.0

2 findings
HIGH Publisher changed: paranoidjk → kgtong (on 2018-05-04) provenance

This version was published by a different npm account than previous versions on 2018-05-04. 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.0.4

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: silentcloud → paranoidjk (on 2018-01-05) provenance

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

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.