kubeagent@0.1.63
AI-powered Kubernetes management CLI
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection found a CLI entry point without install lifecycle hooks, a Kubernetes workload detector, and package-aligned authentication and first-run telemetry. The scanner’s semantic-analysis limitation did not reveal attack behavior in the required detector source.
Static reason
No blocking static signals were detected.
Trigger
Invoking the CLI’s cluster checks, authentication, or first-run telemetry.
Impact
No concrete unauthorized access, secret exfiltration, or destructive behavior was established.
Mechanism
The detector queries Kubernetes resources; authentication uses the configured kubeagent server; first-run telemetry sends limited runtime and machine metadata to that server.
AI rationale
Source inspection found a CLI entry point without install lifecycle hooks, a Kubernetes workload detector, and package-aligned authentication and first-run telemetry. The scanner’s semantic-analysis limitation did not reveal attack behavior in the required detector source.
Network endpoints1
api.kubeagent.net
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and declares no install lifecycle hook.
- The detector reads Kubernetes workload data through kubectl.
- Authentication defaults to kubeagent’s API and app; environment overrides support self-hosted setups.
- First-run telemetry sends CLI version, platform, Node version, and a machine ID to kubeagent’s API.
Evidence against
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 extractFromWorklo
Low
Ai Review Evidence
The detector reads Kubernetes workload data through kubectl.
dist/detector/sources.jsView on unpkg · L10package.jsonView file
7"type": "module",
"bin": {
"kubeagent": "./dist/cli.js"
},
"files": [
"dist",
"README.md",
"LICENSE"
],
"scripts": {
"build": "t
Low
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
LowAi Review Evidencedist/detector/sources.js
LowAi Review Evidencedist/auth.js
Affected versions and remediation
This report applies to kubeagent@0.1.63.
See all versions of kubeagent for other recorded verdicts.
- Review the evidence and your use of kubeagent@0.1.63 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.