registry / @progress/kendo-licensing / 1.11.3
@progress/kendo-licensing@1.11.3
Kendo UI License Manager
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle script performs vendor licensing activation and telemetry, including artifact stamping, but source inspection found no concrete malicious behavior. Static signals are explained by the package's intended commercial-license workflow.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall runs `activate --ignore-no-license`; explicit CLI commands can also activate, authenticate, or download a key.
Impact
Licensing telemetry can include workstation, license, product, and version data; no malicious impact established.
Mechanism
license validation, artifact stamping, and licensing telemetry
AI rationale
The lifecycle script performs vendor licensing activation and telemetry, including artifact stamping, but source inspection found no concrete malicious behavior. Static signals are explained by the package's intended commercial-license workflow.
Evidence
package.jsonbin/kendo-ui-license.jsdist/index.jsdist/index-esm.jsdist/index*.{js,mjs}.next/static/chunks/*.jsnode_modules/.vite/deps/chunk-*.jsnode_modules/.vite/deps/@progress*.js
Network endpoints3
licensing.telerik.comidentity.telerik.com/loginidentity.telerik.com/v2/oauth/telerik/token
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- postinstall runs the licensing CLI activation.
- Activation sends license telemetry including a workstation ID to the Telerik licensing endpoint.
- Activation rewrites license metadata placeholders in package/project build artifacts.
Evidence against
- Behavior is a package-aligned Kendo/Telerik license manager with explicit activate, info, and get-key commands.
- Network use is limited to licensing, OAuth, key-download, and telemetry functions; no remote code loading found.
- No credential harvesting, arbitrary payload execution, destructive action, or AI-agent configuration mutation found.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationTrivialUrlStrings
Source & flagged code
10 flaggedpackage.jsonView file
•scripts.postinstall = node ./bin/kendo-ui-license.js activate --ignore-no-license
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./bin/kendo-ui-license.js activate --ignore-no-license
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/kendo-ui-license.jsView file
1#!/usr/bin/env node
L2: "use strict";var e=require("yargs"),t=require("yargs/helpers"),n=require("child_process"),o=require("readline"),r=require("crypto"),s=require("util"),i=require("fs"),a=require("jso...
High
Child Process
Package source references child process execution.
Findings
8 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/kendo-ui-license.js
HighShellbin/kendo-ui-license.js
HighSame File Env Network Executionbin/kendo-ui-license.js
HighEntrypoint Foreign Package Code Overwritebin/kendo-ui-license.js
HighCommand Output Exfiltrationbin/kendo-ui-license.js
HighSandbox Evasion Gated Capabilitybin/kendo-ui-license.js
HighTrigger Reachable Command Output Exfiltrationbin/kendo-ui-license.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/kendo-ui-license.js
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to @progress/kendo-licensing@1.11.3.
See all versions of @progress/kendo-licensing for other recorded verdicts.
- Review the evidence and your use of @progress/kendo-licensing@1.11.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.