rc-calendar No license 51 versions

rc-calendar

npm Repository Homepage

React Calendar

51

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

afc163benjycuiparanoidjkyesmeckyiminghe

Keywords

reactreact-calendarreact-componentcalendarui componentuicomponent

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from afc163 to zombiej in Jan 2019 is a documented maintainer transition within the react-component org. zombiej is a prolific, established publisher in this ecosystem.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): react-lifecycles-compat is a React core team utility for React 16.3+ lifecycle compatibility. Its addition alongside removal of create-react-class is a standard migration pattern, not a supply chain risk.	ai	2026/04/24

Versions (showing 51 of 217)

View all versions

Version	Deps	Published
9.15.11	7 / 18	2020-06-06
9.15.10	7 / 18	2020-03-13
9.15.9	7 / 18	2019-12-25
9.15.8	7 / 18	2019-11-18
9.15.7	7 / 18	2019-11-09
9.15.6	7 / 18	2019-09-29
9.15.5	7 / 18	2019-07-31
9.15.4	7 / 18	2019-07-15
9.15.3	7 / 18	2019-07-01
9.15.2	7 / 19	2019-06-27
9.15.1	7 / 19	2019-06-25
9.15.0	7 / 19	2019-06-06
9.14.5	7 / 19	2019-05-25
9.13.4	7 / 19	2019-05-16
9.13.3	7 / 19	2019-05-09
9.13.2	7 / 19	2019-04-29
9.13.1	7 / 19	2019-04-08
9.13.0	7 / 19	2019-04-02
9.12.4	7 / 19	2019-04-08
9.12.3	7 / 19	2019-04-01
9.12.1	7 / 19	2019-03-30
9.11.0	7 / 19	2019-03-14
9.10.10	7 / 19	2019-02-23
9.10.9	7 / 19	2019-02-18
9.10.8	7 / 19	2019-01-21
9.10.7	7 / 19	2019-01-18
9.10.6	7 / 19	2019-01-16
9.10.5	7 / 19	2019-01-07
9.10.4	7 / 19	2019-01-03
9.10.3	7 / 19	2019-01-02
9.10.2	7 / 19	2019-01-02
9.10.1	7 / 19	2019-01-02
9.10.0	7 / 19	2019-01-02
9.9.2	7 / 19	2018-12-26
9.9.1	7 / 19	2018-12-24
9.9.0	7 / 19	2018-12-24
9.8.2	7 / 19	2018-12-17
9.8.1	7 / 19	2018-12-06
9.8.0	7 / 19	2018-11-30
9.7.11	7 / 19	2018-10-31
9.7.10	7 / 19	2018-10-09
9.7.9	7 / 19	2018-09-30
9.7.8	7 / 19	2018-09-18
9.7.7	7 / 19	2018-09-08
9.7.6	7 / 19	2018-09-07
9.7.5	7 / 19	2018-09-07
9.7.4	7 / 19	2018-09-03
9.7.3	7 / 19	2018-09-02
9.7.2	7 / 19	2018-09-02
9.7.1	7 / 19	2018-09-02
9.7.0	7 / 19	2018-08-07

v9.15.10

1 finding

LOW No provenance attestation provenance

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

v9.15.9

1 finding

LOW No provenance attestation provenance

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

v9.15.8

1 finding

LOW No provenance attestation provenance

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

v9.15.7

1 finding

LOW No provenance attestation provenance

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

v9.15.6

1 finding

LOW No provenance attestation provenance

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

v9.15.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: zombiej → afc163 (on 2019-07-31) provenance

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

v9.15.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: afc163 → zombiej (on 2019-07-15) provenance

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

v9.15.3

1 finding

LOW No provenance attestation provenance

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

v9.15.2

2 findings

HIGH Publisher changed: zombiej → afc163 (on 2019-06-27) provenance

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

v9.15.1

1 finding

LOW No provenance attestation provenance

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

v9.15.0

1 finding

LOW No provenance attestation provenance

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

v9.14.5

1 finding

LOW No provenance attestation provenance

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

v9.13.4

1 finding

LOW No provenance attestation provenance

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

v9.13.3

1 finding

LOW No provenance attestation provenance

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

v9.13.2

1 finding

LOW No provenance attestation provenance

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

v9.13.1

1 finding

LOW No provenance attestation provenance

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

v9.13.0

1 finding

LOW No provenance attestation provenance

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

v9.12.4

1 finding

LOW No provenance attestation provenance

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

v9.12.3

2 findings

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

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

v9.12.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-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.

v9.11.0

1 finding

LOW No provenance attestation provenance

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

v9.10.10

1 finding

LOW No provenance attestation provenance

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

v9.10.9

1 finding

LOW No provenance attestation provenance

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

v9.10.8

1 finding

LOW No provenance attestation provenance

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

v9.10.7

1 finding

LOW No provenance attestation provenance

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

v9.10.6

1 finding

LOW No provenance attestation provenance

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

v9.10.5

1 finding

LOW No provenance attestation provenance

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

v9.10.4

1 finding

LOW No provenance attestation provenance

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

v9.10.3

1 finding

LOW No provenance attestation provenance

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

v9.10.2

1 finding

LOW No provenance attestation provenance

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

v9.10.1

1 finding

LOW No provenance attestation provenance

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

v9.10.0

2 findings

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

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

v9.9.2

1 finding

LOW No provenance attestation provenance

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

v9.9.1

1 finding

LOW No provenance attestation provenance

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

v9.9.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: zombiej → afc163 (on 2018-12-24) provenance

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

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

v9.8.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 2018-12-06) provenance

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

v9.8.0

1 finding

LOW No provenance attestation provenance

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

v9.7.11

1 finding

LOW No provenance attestation provenance

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

v9.7.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: yesmeck → zombiej (on 2018-10-09) provenance

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

v9.7.9

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 → yesmeck (on 2018-09-30) provenance

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

v9.7.8

1 finding

LOW No provenance attestation provenance

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

v9.7.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-09-08) provenance

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

v9.7.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 2018-09-07) provenance

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

v9.7.5

1 finding

LOW No provenance attestation provenance

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

v9.7.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: afc163 → zombiej (on 2018-09-03) provenance

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

v9.7.3

1 finding

LOW No provenance attestation provenance

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

v9.7.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: yesmeck → afc163 (on 2018-09-02) provenance

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

v9.7.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: yesmeck → afc163 (on 2018-09-02) provenance

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

v9.7.0

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.