@progress/kendo-angular-dateinputs No license 22 versions

@progress/kendo-angular-dateinputs

npm Homepage

22

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

progress

Keywords

AngularKendo UIangular dateinputangularjscalendardate-inputdate-pickerdate-timedateinputdateinput for angulardaterangedatetimepickermultiviewcalendartimepicker

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Progress/Telerik migrated publishing to GitHub Actions CI; consistent with org-wide automation pattern across their large package portfolio.	ai	2026/05/04
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit dependency pattern is stable for this package.	ai	2026/04/30
dependencies	unvetted-dep:@progress/kendo-common	AI (dependencies): Same @progress org scope as this package; stable internal dependency.	ai	2026/04/30
dependencies	unvetted-dep:@progress/kendo-angular-schematics	AI (dependencies): Same @progress org scope; schematics tooling dependency, stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@progress/kendo-angular-schematics	AI (phantom-deps): Schematics dep declared for ng-add support; not directly imported in runtime code — stable false positive for this package.	ai	2026/04/29

Versions (showing 22 of 22)

Version	Deps	Published
24.0.3	5 / 0	2026-05-29
24.0.2	5 / 0	2026-05-28
24.0.1	5 / 0	2026-05-21
24.0.0	5 / 0	2026-05-20
23.4.0	5 / 0	2026-04-24
23.3.0	5 / 0	2026-04-02
23.2.2	5 / 0	2026-03-18
23.2.1	5 / 0	2026-03-17
23.2.0	5 / 0	2026-02-27
23.1.0	5 / 0	2026-02-18
23.0.1	5 / 0	2026-02-11
23.0.0	5 / 0	2026-02-10
22.0.1	5 / 0	2026-01-15
22.0.0	5 / 0	2026-01-14
21.4.1	5 / 0	2026-01-14
21.4.0	5 / 0	2026-01-12
21.3.0	5 / 0	2025-12-11
21.2.0	5 / 0	2025-12-03
21.1.0	6 / 0	2025-11-20
21.0.1	6 / 0	2025-11-19
21.0.0	6 / 0	2025-11-12
20.1.2	6 / 0	2025-11-28

v24.0.3

1 finding

LOW No provenance attestation provenance

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

v24.0.2

1 finding

LOW No provenance attestation provenance

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

v24.0.1

1 finding

LOW No provenance attestation provenance

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

v24.0.0

1 finding

LOW No provenance attestation provenance

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

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

v23.2.2

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-03-18) provenance

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

v23.2.1

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-03-17) provenance

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

v23.2.0

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-02-27) provenance

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

v23.1.0

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-02-18) provenance

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

v23.0.1

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-02-11) provenance

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

v23.0.0

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-02-10) provenance

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

v22.0.1

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-01-15) provenance

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

v22.0.0

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-01-14) provenance

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

v21.4.1

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-01-14) provenance

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

v21.4.0

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2026-01-12) provenance

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

v21.3.0

2 findings

HIGH Publisher changed: progress → GitHub Actions (on 2025-12-11) provenance

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

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

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

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

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

v20.1.2

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.