rc-checkbox MIT 50 versions

rc-checkbox

npm Repository Homepage

checkbox ui component for react

50

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

afc163yiminghezombiejraohaimadccc

Keywords

reactreact-componentreact-checkboxcheckbox

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): afc163 → madccc is a known Ant Design team transition; both are established react-component org members.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): madccc is a known Ant Design ecosystem maintainer with extensive publish history.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Cleanup of inactive react-component org members during major version bump.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): rc-util is the canonical shared utility for the react-component ecosystem; expected dependency.	ai	2026/04/24

Versions (showing 50 of 50)

Version	Deps	Published
3.5.0	3 / 26	2024-11-20
3.4.0	3 / 26	2024-11-19
3.3.0	3 / 26	2024-05-17
3.2.0	3 / 26	2024-02-29
3.1.0	3 / 24	2023-06-14
3.0.1	3 / 24	2023-05-10
3.0.0	3 / 24	2023-03-07
2.3.2	2 / 14	2020-12-08
2.3.1	2 / 14	2020-07-15
2.3.0	2 / 14	2020-07-09
2.2.0	2 / 10	2020-03-30
2.1.8	4 / 10	2019-09-24
2.1.7	4 / 10	2019-06-05
2.1.6	4 / 10	2018-12-23
2.1.5	4 / 10	2018-02-24
2.1.4	4 / 10	2018-01-29
2.1.3	4 / 10	2018-01-28
2.1.2	4 / 10	2018-01-25
2.1.1	4 / 10	2017-11-16
2.1.0	4 / 10	2017-11-15
2.0.3	4 / 7	2017-05-31
2.0.2	4 / 6	2017-05-23
2.0.1	4 / 6	2017-05-18
2.0.0	3 / 6	2017-04-14
1.5.0	2 / 6	2017-02-28
1.4.4	2 / 6	2017-02-03
1.4.3	2 / 6	2016-10-28
1.4.2	2 / 6	2016-09-13
1.4.1	2 / 6	2016-08-05
1.4.0	2 / 6	2016-06-12
1.3.7	1 / 6	2016-06-02
1.3.6	1 / 6	2016-05-24
1.3.5	1 / 6	2016-05-19
1.3.4	1 / 6	2016-04-25
1.3.3	1 / 6	2016-04-08
1.3.2	1 / 7	2016-03-22
1.3.1	1 / 7	2016-03-22
1.3.0	1 / 7	2016-02-20
1.2.0	1 / 7	2015-11-17
1.1.2	1 / 5	2015-11-16
1.1.1	1 / 5	2015-08-11
1.1.0	1 / 5	2015-08-10
1.0.6	1 / 5	2015-07-16
1.0.5	1 / 5	2015-07-16
1.0.4	1 / 5	2015-07-16
1.0.3	1 / 5	2015-07-16
1.0.2	1 / 5	2015-07-16
1.0.1	1 / 5	2015-07-16
1.0.0	1 / 5	2015-07-15
0.0.1	1 / 5	2015-07-15

v3.2.0

2 findings

HIGH Publisher changed: afc163 → zombiej (on 2024-02-29) provenance

This version was published by a different npm account than previous versions on 2024-02-29. 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.

v3.1.0

2 findings

HIGH Publisher changed: zombiej → afc163 (on 2023-06-14) provenance

This version was published by a different npm account than previous versions on 2023-06-14. 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.

v3.0.1

2 findings

HIGH Publisher changed: afc163 → zombiej (on 2023-05-10) provenance

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

v3.0.0

2 findings

HIGH Publisher changed: afc163 → madccc (on 2023-03-07) provenance

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

1 finding

LOW No provenance attestation provenance

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

v2.3.1

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

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

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

1 finding

LOW No provenance attestation provenance

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

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 → afc163 (on 2018-02-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-24. 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

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

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: paranoidjk → yesmeck (on 2017-11-15) provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

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

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 → paranoidjk (on 2017-04-14) provenance

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