macOS
Homebrew已验证 · 100%
brew install kconflocal Homebrew formula metadata
安装
其他安装命令
Linux
Nix已验证 · 92%
nix profile install nixpkgs#kconfnixpkgs package indexes · pkgs/by-name/kc/kconf/package.nix · 来源: api.github.com
概览
软件包摘要
CLI for managing multiple kubeconfigs
历史
项目历史与用法
kconf is an opinionated command-line tool for managing multiple kubeconfig entries in the default Kubernetes config file.
项目历史
The repository was created in January 2020. Its README explains the motivation as replacing shell automation around the KUBECONFIG environment variable with commands that merge, list, view, remove, and switch contexts in $HOME/.kube/config.
采用历史
The batch input records Homebrew and Nix packages. Upstream release history shows rapid 1.x releases during 2020 and a 2.0.0 release on November 17, 2023.
使用方式
kconf is used to add kubeconfig files, optionally rename contexts on import, list contexts, print one context's config, switch contexts, and set namespaces while leaving kubectl pointed at its default config path.
为什么软件包爱好者会关心
kconf is a small example of Kubernetes CLI tooling that wraps a common dotfile workflow instead of introducing a new service or database. Its package value is convenience: one executable for a task many operators otherwise solve with shell snippets.
时间线
- 2020-01-14: GitHub repository created.
- 2020-01-21: v1.0.0 first stable release published.
- 2020-04-03: v1.1.2 added a view command for extracting a single kubeconfig.
- 2023-11-17: v2.0.0 release published.
Related projects
- kconf's workflow is built around kubectl's default use of $HOME/.kube/config and the Kubernetes kubeconfig format.
来源
安全态势
风险级别：绿色
narrow executable package without higher-risk signals.
风险分类器
绿色 风险 · 低 置信度 · appliance
原因
- narrow executable package without higher-risk signals
信号
- metadata:no-higher-risk-signals
安装行为
- formula 元数据中未记录 Homebrew post-install 钩子。
- Homebrew bottle 元数据适用于 6 个平台目标。
- 构建元数据列出 1 个构建依赖。
建议审查
在无人值守的代理使用前，请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
~/.kube/config
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.kube/config
可执行文件
已安装的可执行文件
| 命令 | 类型 | 暴露范围 | 备注 |
|---|---|---|---|
kconf | cli | 全局可执行文件 |
新鲜度
版本和新鲜度
这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时，才会提示版本落后。
页面生成时间2026-07-25
管理器版本2.0.0
管理器更新时间
本地数据OK
上游当前
检测到的最新版本v2.0.0
https://github.com/particledecay/kconf
- 信息No package-manager update timestamp was available.低 置信度
安装元数据
软件包元数据
| 软件包键 | brew:kconf |
|---|---|
| 版本 | 2.0.0 |
| 软件包管理器 | Homebrew |
| 软件包管理器页面 | https://formulae.brew.sh/formula/kconf |
| 主页 | https://github.com/particledecay/kconf |
| 仓库 | https://github.com/particledecay/kconf |
| 上游文档 | https://github.com/particledecay/kconf#readme |
| 许可证 | MIT |
| 源码归档 | https://github.com/particledecay/kconf/archive/refs/tags/v2.0.0.tar.gz |
| 构建依赖 | go |
| Bottle | 可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | 未定义 |
| 服务 | 未声明 |
注册表事实
源数据库详情
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | kconf |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
源数据库匹配
其他软件包管理器记录
匹配项来自外部软件包管理器索引，并与本地 Automic Vault 软件包链接分开显示。
Nix95%
kconf
nix profile install nixpkgs#kconf- normalized package name match
- 匹配方式：Kconf
来源线索
由仓库数据生成
此页面由 av-web 从 scripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。
Combined YAML source
View the package source record on GitHub.
使用的来源
- Geiger risk classifier
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment