kubeagent@0.1.70
AI-powered Kubernetes management CLI
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or confirmed attack behavior. The automatic one-time telemetry is package-aligned and sends platform metadata to the package’s own API, so the verdict is clean.
Static reason
No blocking static signals were detected.
Trigger
Running the CLI after command parsing.
Impact
This reports basic usage metadata; the inspected payload does not include account credentials or establish a concrete attack surface.
Mechanism
The CLI sends its version, operating system, architecture, Node.js version, and a stable per-machine identifier.
AI rationale
Source inspection found no install lifecycle hook or confirmed attack behavior. The automatic one-time telemetry is package-aligned and sends platform metadata to the package’s own API, so the verdict is clean.
Network endpoints1
api.kubeagent.net/telemetry
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and contains build, development, and test scripts, with no install lifecycle hook.
- The required detector source inspects Kubernetes workload metadata and deployed Helm release metadata.
- After parsing a CLI command, the entrypoint calls telemetry once per machine; the payload contains CLI and platform versions plus a machine identifier, and is sent to the package’s API.
- Authentication and API-key operations use the configured or package-default KubeAgent server; the inspected telemetry payload does not include those credentials.
Evidence against
- The CLI sends first-run telemetry automatically, using a stable per-machine identifier.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/detector/sources.jsView file
•stage = ast_semantic_analysis; reason = ast_alias_growth_limit_exceeded; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/detector/sources.jsView on unpkg10async function fetchWorkload(kind, resource, options) {
return (await kubectlJson(["get", resource, "--all-namespaces"], options));
}
function extractFromWorkload(kind, w) {
Low
Ai Review Evidence
The required detector source inspects Kubernetes workload metadata and deployed Helm release metadata.
dist/detector/sources.jsView on unpkg · L10package.jsonView file
8"bin": {
"kubeagent": "./dist/cli.js"
},
"files": [
"dist",
"README.md",
"LICENSE"
],
"scripts": {
"build": "tsc --build",
"dev": "tsx src/cli.ts",
"test": "vitest run",
"test:wa
Findings
1 High3 Medium8 Low
HighSemantic Analysis Limiteddist/detector/sources.js
MediumNetwork
MediumEnvironment Vars
MediumWildcard Dependency
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/detector/sources.js
Affected versions and remediation
This report applies to kubeagent@0.1.70.
See all versions of kubeagent for other recorded verdicts.
- Review the evidence and your use of kubeagent@0.1.70 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.