kavrix 0.2.5 → 0.2.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +22 -4
- package/dist/bin.js +2096 -136
- package/dist/chunks/{chunk-7AJQTDJG.js → chunk-O5SD3CYP.js} +3 -2
- package/dist/chunks/{chunk-MNQHU3EJ.js → chunk-PMIKDBMJ.js} +181 -2
- package/dist/chunks/{chunk-3LXISP6O.js → chunk-S5YN7S73.js} +1 -1
- package/dist/chunks/{chunk-MTADWNBJ.js → chunk-ZNVQXSGS.js} +2 -2
- package/dist/index.d.ts +1 -1
- package/dist/index.js +1 -1
- package/dist/kavrix.cdx.json +20 -20
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -41,6 +41,13 @@ kavrix db vault create --profile work
|
|
|
41
41
|
# 3. Copy the returned opaque vault ID into the flat commands.
|
|
42
42
|
kavrix put github/token --profile work --vault <vault-id>
|
|
43
43
|
kavrix get github/token --reveal --profile work --vault <vault-id>
|
|
44
|
+
|
|
45
|
+
# Or create an explicit project/service/item hierarchy.
|
|
46
|
+
kavrix context create platform --environment production --profile work --vault <vault-id>
|
|
47
|
+
kavrix service create github --context platform --profile work --vault <vault-id>
|
|
48
|
+
kavrix item create deploy --context platform --service github --profile work --vault <vault-id>
|
|
49
|
+
kavrix field set token --type api-key --context platform --service github \
|
|
50
|
+
--item deploy --profile work --vault <vault-id>
|
|
44
51
|
```
|
|
45
52
|
|
|
46
53
|
Sensitive input is prompted for or read from stdin; it is never accepted as a
|
|
@@ -57,6 +64,7 @@ options in your installed version.
|
|
|
57
64
|
| `db key create` | Create an exact-snapshot key for full local-file sharing. |
|
|
58
65
|
| `db recovery ...` | Manage database-root recovery kits. |
|
|
59
66
|
| `migrate database` | Copy one legacy version 2 vault into a database. |
|
|
67
|
+
| `context`, `service`, `item`, `field` | Manage structured project credentials and schema-driven typed fields. |
|
|
60
68
|
| `put`, `get`, `list`, `view`, `search`, `stats`, `has`, `rename`, `remove` | Store, read, and organize credentials. |
|
|
61
69
|
| `key status/verify/copy/replicate/assign/rewrap` | Manage protected key files. |
|
|
62
70
|
| `recovery create/verify/status/revoke/use` | Manage recovery kits. |
|
|
@@ -68,8 +76,16 @@ options in your installed version.
|
|
|
68
76
|
| `audit` | Plaintext-free security audit trail. |
|
|
69
77
|
| `agent run`, `agent exec` | Credential firewall that brokers AI coding agents. |
|
|
70
78
|
|
|
71
|
-
|
|
72
|
-
commands never display
|
|
79
|
+
Sensitive plaintext output is opt-in through `--reveal` or multiline-safe
|
|
80
|
+
`--reveal-base64`; listing and dashboard commands never display field values.
|
|
81
|
+
`field get` may return a non-sensitive value according to its schema.
|
|
82
|
+
|
|
83
|
+
Database vaults organize private data as project context/environment →
|
|
84
|
+
service/group → credential item → typed fields. The root flat commands remain
|
|
85
|
+
a compatibility projection over the default context/service and never split a
|
|
86
|
+
literal name such as `github/token` into hierarchy segments. Field definitions
|
|
87
|
+
carry copy, reveal, reauthentication, and export policies; present values stay
|
|
88
|
+
redacted until an allowed explicit reveal.
|
|
73
89
|
|
|
74
90
|
## Running tools without pasting secrets
|
|
75
91
|
|
|
@@ -107,6 +123,7 @@ authorization sidecar.
|
|
|
107
123
|
| `--value-stdin` | Read a credential value from stdin. |
|
|
108
124
|
| `--secrets-stdin` | Read every unlock secret from exact stdin frames. |
|
|
109
125
|
| `--reveal` | The explicit guard that prints plaintext. |
|
|
126
|
+
| `--reveal-base64` | Authorized multiline-safe field-value output. |
|
|
110
127
|
| `--json` | Masked machine-readable output. |
|
|
111
128
|
| `--overwrite` | Opt in to replacing something that already exists. |
|
|
112
129
|
| `--allow-insecure-transport` | Explicit opt-in to unencrypted MongoDB transport (isolated networks only). |
|
|
@@ -132,8 +149,9 @@ must explicitly enable validated TLS.
|
|
|
132
149
|
- Losing all valid owner keys and all database recovery kits makes the database
|
|
133
150
|
permanently unrecoverable by design; there is no reset or escrow.
|
|
134
151
|
- User identities, public enrollment, per-vault grants and roles, revocation
|
|
135
|
-
with rotation, ownership transfer
|
|
136
|
-
|
|
152
|
+
with rotation, and ownership transfer are not yet implemented. Structured
|
|
153
|
+
payloads model notes, attachment ownership, and history, but 0.2.6 does not
|
|
154
|
+
add attachment transfer or history-restore commands.
|
|
137
155
|
- Windows command scripts (`.bat`, `.cmd`, `.com`) are refused for execution;
|
|
138
156
|
invoke real executables.
|
|
139
157
|
|