@progress/kendo-react-scheduler SEE LICENSE IN LICENSE.md 16 versions

@progress/kendo-react-scheduler

npm Repository Homepage

React Scheduler brings the functionality of Outlook's Calendar to a single UI component. KendoReact Scheduler package

16

Versions

SEE LICENSE IN LICENSE.md

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

progress

Keywords

Kendo UIReactProgressSchedulerKendoReactreactjsScheduler viewRecurring eventTimezone supportTelerikcomponentsReact component

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@progress/kendo-draggable	AI (dependencies): Same @progress org scope; stable sibling dependency across KendoReact versions.	ai	2026/05/17
dependencies	unvetted-dep:@progress/kendo-recurrence	AI (dependencies): Same @progress org scope; stable sibling dependency across KendoReact versions.	ai	2026/05/17
provenance	no-provenance	AI (provenance): Progress/Telerik publishes via GitHub Actions without Sigstore attestation; consistent across all KendoReact packages.	ai	2026/05/17
phantom-deps	phantom-dep:@progress/kendo-draggable	AI (phantom-deps): Same-org @progress scope; declared as runtime dep, indirect usage pattern is stable for this package.	ai	2026/04/29

Versions (showing 16 of 16)

Version	Deps	Published
15.0.0	3 / 0	2026-05-20
14.4.1	3 / 0	2026-05-04
14.4.0	3 / 0	2026-04-17
14.3.2	3 / 0	2026-04-07
14.3.1	3 / 0	2026-04-03
14.3.0	3 / 0	2026-04-02
14.2.1	3 / 0	2026-03-06
14.2.0	3 / 0	2026-02-19
14.1.1	3 / 0	2026-02-16
14.1.0	3 / 0	2026-02-13
14.0.1	3 / 0	2026-02-12
14.0.0	3 / 0	2026-02-10
13.3.0	3 / 0	2026-01-16
13.2.0	3 / 0	2025-12-17
13.1.0	3 / 0	2025-11-18
13.0.0	3 / 0	2025-11-11

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

v14.4.1

1 finding

LOW No provenance attestation provenance

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

v14.3.2

1 finding

LOW No provenance attestation provenance

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

v14.3.1

1 finding

LOW No provenance attestation provenance

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

v14.3.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.

v14.2.1

1 finding

LOW No provenance attestation provenance

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

v14.2.0

1 finding

LOW No provenance attestation provenance

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

v14.1.1

1 finding

LOW No provenance attestation provenance

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

v14.1.0

1 finding

LOW No provenance attestation provenance

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

v14.0.1

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.

v14.0.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.

v13.3.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.

v13.2.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.

v13.1.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.

v13.0.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.