← Home

@progress/kendo-angular-utils

Kendo UI Angular utils component

26
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

AngularKendo UIUtilsProgress

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Progress/Telerik migrated Kendo Angular publishing to GitHub Actions CI/CD; consistent across the package's large version history. ai
provenance no-provenance AI (provenance): Progress/Telerik publishes via GitHub Actions without Sigstore attestation; consistent across their package ecosystem. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package family. ai
phantom-deps phantom-dep:@progress/kendo-angular-schematics AI (phantom-deps): Same-org schematics package; not directly imported in source but used via schematics entry point — stable false positive. ai

Versions (showing 26 of 26)

Version Deps Published
24.2.2 3 / 0
24.2.1 3 / 0
24.2.0 3 / 0
24.1.0 3 / 0
24.0.3 3 / 0
24.0.2 3 / 0
24.0.1 3 / 0
24.0.0 3 / 0
23.4.0 3 / 0
23.3.0 3 / 0
23.2.2 3 / 0
23.2.1 3 / 0
23.2.0 3 / 0
23.1.0 3 / 0
23.0.1 3 / 0
23.0.0 3 / 0
22.0.1 3 / 0
22.0.0 3 / 0
21.4.1 3 / 0
21.4.0 3 / 0
21.3.0 3 / 0
21.2.0 3 / 0
21.1.0 3 / 0
21.0.1 3 / 0
21.0.0 3 / 0
20.1.2 3 / 0

v24.2.2

1 finding
INFO No provenance attestation provenance

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

v24.2.1

1 finding
INFO No provenance attestation provenance

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

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