rc-form — Greenflagged

React High Order Form Component

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

benjycuiyesmeckafc163yiminghenikoguddcat1115zombiej

Keywords

reactreact-componentreact-formform

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): Added lodash.get/has/set are legitimate, well-known lodash utilities appropriate for a form library doing nested field path operations. No malicious signal.	ai	2026/04/24
dependencies	unvetted-dep:lodash.set	AI (dependencies): lodash.set is a well-known, widely-used utility module with no known security issues; stable false positive for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Established package (10+ years old) published before Sigstore provenance was standard; low risk signal for this package.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is explained by addition of legitimate dist build artifacts (UMD bundle, minified bundle, source map) that were absent in prior versions.	ai	2026/04/24
source-diff	net-exec-file:dist/rc-form.js	AI (source-diff): dist/rc-form.js is a standard webpack UMD bundle for a React form library; the 'network+exec' trigger fires on webpack's module execution boilerplate, not actual network/dropper behavior.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from afc163 to benjycui occurred in 2017 as part of a legitimate react-component org transition; both are known Ant Design ecosystem contributors.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are all known Ant Design / react-component ecosystem contributors; this was a legitimate org-level maintainer expansion in 2017.	ai	2026/04/24

Versions (showing 86 of 86)

Version	Deps	Published
2.4.12	9 / 16	2020-12-30
2.4.11	8 / 16	2019-11-19
2.4.10	8 / 16	2019-11-09
2.4.9	7 / 16	2019-09-27
2.4.8	7 / 16	2019-07-01
2.4.7	7 / 16	2019-06-30
2.4.6	7 / 16	2019-06-20
2.4.5	7 / 16	2019-05-10
2.4.4	7 / 16	2019-03-30
2.4.3	7 / 16	2019-03-01
2.4.2	7 / 16	2019-02-15
2.4.1	7 / 16	2019-01-12
2.4.0	7 / 16	2018-12-21
2.3.0	7 / 16	2018-12-17
2.2.7	7 / 16	2018-12-04
2.2.6	7 / 16	2018-10-18
2.2.5	7 / 16	2018-10-15
2.2.4	7 / 16	2018-10-09
2.2.3	7 / 16	2018-09-16
2.2.2	7 / 16	2018-09-05
2.2.1	7 / 16	2018-07-11
2.2.0	7 / 16	2018-04-04
2.1.7	7 / 16	2017-12-25
2.1.6	7 / 16	2017-12-14
2.1.5	7 / 16	2017-12-08
2.1.4	7 / 16	2017-12-03
2.1.3	7 / 16	2017-11-27
2.1.2	7 / 16	2017-11-27
2.1.1	7 / 16	2017-11-27
2.1.0	7 / 16	2017-11-22
2.0.0	7 / 16	2017-11-09
1.5.0	7 / 16	2017-10-31
1.4.8	7 / 16	2017-09-14
1.4.7	7 / 16	2017-08-23
1.4.6	7 / 16	2017-08-09
1.4.5	7 / 16	2017-08-09
1.4.4	7 / 16	2017-08-09
1.4.3	7 / 16	2017-06-20
1.3.2	9 / 14	2017-05-18
1.3.0	8 / 14	2017-01-06
1.1.0	8 / 14	2016-12-28
1.0.1	5 / 13	2016-10-11
1.0.0	4 / 13	2016-08-29
0.17.2	4 / 13	2016-08-02
0.17.1	3 / 13	2016-06-12
0.17.0	3 / 13	2016-06-12
0.16.0	3 / 13	2016-05-19
0.15.4	3 / 14	2016-05-11
0.15.3	3 / 14	2016-05-09
0.15.2	3 / 14	2016-04-25
0.15.1	3 / 14	2016-04-08
0.15.0	3 / 14	2016-03-30
0.14.1	3 / 14	2016-03-02
0.14.0	3 / 14	2016-02-27
0.13.6	3 / 14	2016-02-26
0.13.5	3 / 14	2016-02-23
0.13.4	3 / 14	2016-02-15
0.13.3	3 / 14	2016-02-15
0.13.2	3 / 14	2016-02-15
0.13.0	3 / 15	2016-02-14
0.12.1	2 / 16	2016-02-03
0.12.0	2 / 16	2016-02-03
0.11.0	2 / 15	2016-02-02
0.10.4	2 / 15	2016-02-01
0.10.3	2 / 15	2016-01-28
0.10.2	2 / 15	2016-01-28
0.10.1	2 / 15	2016-01-28
0.10.0	2 / 14	2016-01-27
0.9.1	2 / 13	2016-01-21
0.9.0	2 / 13	2016-01-18
0.8.0	2 / 13	2016-01-13
0.7.3	2 / 13	2016-01-06
0.7.2	2 / 13	2016-01-06
0.7.1	2 / 13	2016-01-05
0.7.0	2 / 13	2015-12-29
0.6.0	2 / 13	2015-12-28
0.5.1	2 / 13	2015-12-15
0.5.0	2 / 13	2015-12-15
0.4.2	2 / 14	2015-12-15
0.4.1	2 / 14	2015-12-15
0.4.0	2 / 14	2015-12-14
0.3.1	2 / 14	2015-12-14
0.3.0	2 / 12	2015-12-11
0.2.0	2 / 10	2015-12-10
0.1.0	2 / 8	2015-12-09
0.0.0	0 / 7	2015-12-08

v2.4.11

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: afc163 → zombiej (on 2019-11-19) provenance

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

v2.4.10

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: zombiej → afc163 (on 2019-11-09) provenance

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

v2.4.9

1 finding

LOW No provenance attestation provenance

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

v2.4.8

2 findings

HIGH New file with network + code execution: dist/rc-form.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v2.4.7

2 findings

HIGH New file with network + code execution: dist/rc-form.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v2.4.6

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: afc163 → zombiej (on 2019-06-20) provenance

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

v2.4.5

1 finding

LOW No provenance attestation provenance

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

v2.4.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: zombiej → afc163 (on 2019-03-30) provenance

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

v2.4.3

2 findings

HIGH Publisher changed: afc163 → zombiej (on 2019-03-01) provenance

This version was published by a different npm account than previous versions on 2019-03-01. 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.

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.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: zombiej → afc163 (on 2019-01-12) provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.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: afc163 → zombiej (on 2018-12-17) provenance

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

v2.2.7

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: zombiej → afc163 (on 2018-12-04) provenance

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

v2.2.6

1 finding

LOW No provenance attestation provenance

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

v2.2.5

1 finding

LOW No provenance attestation provenance

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

v2.2.4

1 finding

LOW No provenance attestation provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.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: benjycui → zombiej (on 2018-09-05) provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.7

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: benjycui → afc163 (on 2017-12-25) provenance

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

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

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: yesmeck → benjycui (on 2017-12-08) provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.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: benjycui → yesmeck (on 2017-11-27) provenance

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

v2.1.1

2 findings

HIGH Publisher changed: afc163 → benjycui (on 2017-11-27) provenance

This version was published by a different npm account than previous versions on 2017-11-27. 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.

v2.1.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: benjycui → afc163 (on 2017-11-22) provenance

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

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.5.0

1 finding

INFO No provenance attestation provenance

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

v1.4.8

1 finding

INFO No provenance attestation provenance

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

v1.4.7

1 finding

INFO No provenance attestation provenance

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

v1.4.6

1 finding

INFO No provenance attestation provenance

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

v1.4.5

1 finding

INFO No provenance attestation provenance

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

v1.4.4

1 finding

INFO No provenance attestation provenance

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

v1.4.3

1 finding

INFO No provenance attestation provenance

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

v1.3.2

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: yiminghe → benjycui (on 2017-05-18) provenance

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

v1.3.0

1 finding

INFO No provenance attestation provenance

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

v1.1.0

1 finding

INFO No provenance attestation provenance

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

v1.0.1

1 finding

INFO No provenance attestation provenance

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

v1.0.0

1 finding

INFO No provenance attestation provenance

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