@progress/kendo-react-scheduler
React Scheduler brings the functionality of Outlook's Calendar to a single UI component. KendoReact Scheduler package
17
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, so a manually published version cannot be tied back to a reviewed commit.
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 | |
| dependencies | unvetted-dep:@progress/kendo-recurrence | AI (dependencies): Same @progress org scope; stable sibling dependency across KendoReact versions. | ai | |
| provenance | no-provenance | AI (provenance): Progress/Telerik publishes via GitHub Actions without Sigstore attestation; consistent across all KendoReact packages. | ai | |
| 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 |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 15.1.0 | 3 / 0 | |
| 15.0.0 | 3 / 0 | |
| 14.4.1 | 3 / 0 | |
| 14.4.0 | 3 / 0 | |
| 14.3.2 | 3 / 0 | |
| 14.3.1 | 3 / 0 | |
| 14.3.0 | 3 / 0 | |
| 14.2.1 | 3 / 0 | |
| 14.2.0 | 3 / 0 | |
| 14.1.1 | 3 / 0 | |
| 14.1.0 | 3 / 0 | |
| 14.0.1 | 3 / 0 | |
| 14.0.0 | 3 / 0 | |
| 13.3.0 | 3 / 0 | |
| 13.2.0 | 3 / 0 | |
| 13.1.0 | 3 / 0 | |
| 13.0.0 | 3 / 0 |
v15.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.