rc-rate
React Star Rate Component
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by TypeScript migration and dual CJS/ESM output (lib + es dirs); no obfuscation or injected payloads. | ai | |
| provenance | publisher-changed | AI (provenance): afc163 is a well-known Ant Design/react-component ecosystem maintainer; transition from yiminghe is a legitimate org-level handoff within react-component GitHub org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (benjycui, yesmeck, yutingzhao1991, zombiej) are all known contributors to the Ant Design/react-component ecosystem; legitimate team expansion. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @babel/runtime and rc-util are established, well-known packages in the Ant Design ecosystem; standard additions for a TypeScript/ESM refactor. | ai | |
| provenance | no-provenance | AI (provenance): rc-rate is a long-established package from the react-component org; lack of Sigstore provenance is not a meaningful risk signal for this publisher. | ai | |
| dependencies | unvetted-dep:rc-util | AI (dependencies): rc-util is a standard utility library from the same react-component ecosystem used across all rc-* packages; not a risk. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 2.13.1 | 3 / 22 | |
| 2.13.0 | 3 / 21 | |
| 2.12.0 | 3 / 20 | |
| 2.11.2 | 3 / 20 | |
| 2.11.1 | 3 / 20 | |
| 2.11.0 | 3 / 20 | |
| 2.10.0 | 3 / 20 | |
| 2.9.3 | 3 / 20 | |
| 2.9.2 | 3 / 20 | |
| 2.9.1 | 3 / 16 | |
| 2.9.0 | 3 / 16 | |
| 2.8.2 | 3 / 16 | |
| 2.8.1 | 3 / 16 | |
| 2.8.0 | 3 / 16 | |
| 2.7.0 | 3 / 16 | |
| 2.6.0 | 2 / 15 | |
| 2.5.1 | 4 / 8 | |
| 2.5.0 | 4 / 8 | |
| 2.4.3 | 5 / 8 | |
| 2.4.2 | 4 / 8 | |
| 2.4.1 | 4 / 8 | |
| 2.4.0 | 4 / 8 | |
| 2.3.0 | 4 / 8 | |
| 2.2.0 | 3 / 7 | |
| 2.1.1 | 2 / 5 | |
| 2.1.0 | 1 / 6 | |
| 2.0.1 | 1 / 6 | |
| 2.0.0 | 1 / 6 | |
| 1.1.2 | 0 / 6 | |
| 1.1.1 | 0 / 6 | |
| 1.1.0 | 0 / 6 | |
| 1.0.1 | 0 / 6 | |
| 1.0.0 | 0 / 6 |
v2.13.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-02-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.13.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-05-30. This could indicate a legitimate maintainer transition or an account compromise.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-12. This could indicate a legitimate maintainer transition or an account compromise.
v2.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-18. This could indicate a legitimate maintainer transition or an account compromise.
v2.9.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-17. This could indicate a legitimate maintainer transition or an account compromise.
v2.9.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-02. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-15. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.1
2 findingsThis version was published by a different npm account than previous versions on 2020-06-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.7.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-29. This could indicate a legitimate maintainer transition or an account compromise.
v2.6.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-16. This could indicate a legitimate maintainer transition or an account compromise.
v2.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-02-04. This could indicate a legitimate maintainer transition or an account compromise.
v2.5.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.
v2.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-11. This could indicate a legitimate maintainer transition or an account compromise.
v2.4.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-11. This could indicate a legitimate maintainer transition or an account compromise.
v2.4.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.
v2.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-21. This could indicate a legitimate maintainer transition or an account compromise.
v2.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-08. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-04-20. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-06. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-20. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.