replume-cli 0.1.1 → 0.1.2

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 CHANGED
@@ -13,6 +13,7 @@ npm install -g replume-cli
13
13
  ```
14
14
 
15
15
  Cursor hooks are installed by `replume init --cursor`, or automatically when the project already has a `.cursor/` directory and you run `replume init`; otherwise Cursor agent steps will not be recorded in the ledger.
16
+ Codex hooks are installed by `replume init --codex`, or automatically when the project already has a `.codex/` directory and you run `replume init`; finding `codex` on PATH alone does not install them. Otherwise Codex agent steps will not be recorded in the ledger. After installation, review and trust the hook definition with `/hooks` in Codex.
16
17
 
17
18
  Create a disposable project in a scratch directory. If Git asks for an identity when you commit, set `git config user.name "Your Name"` and `git config user.email "you@example.com"` in this disposable repository.
18
19
 
@@ -71,7 +72,7 @@ console.log(`ADD=${add(1, 2)}`);
71
72
  JS
72
73
  ```
73
74
 
74
- Cursor project hooks are installed by `replume init` only when `.cursor/` already exists in the project or `--cursor` is supplied. The global install keeps `replume hook claude` and `replume hook cursor` available to hooks. A one-shot npx does not leave a persistent hook command. If npm returns 404, the package has not been published yet.
75
+ Cursor project hooks are installed by `replume init` only when `.cursor/` already exists in the project or `--cursor` is supplied. Codex project hooks follow the same opt-in rule with `.codex/` or `--codex`. The global install keeps `replume hook claude`, `replume hook cursor`, and `replume hook codex` available to hooks. A one-shot npx does not leave a persistent hook command. If npm returns 404, the package has not been published yet.
75
76
 
76
77
  To remove Replume's project hooks, run `replume init --remove-cursor-hooks` for Cursor. For Claude Code, edit the project's `.claude/settings.json` and remove only the `replume hook claude` entries, keeping any other hooks. `replume init` does not currently have a Claude hook removal flag.
77
78
 
@@ -30,3 +30,31 @@ CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
30
30
  TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
31
31
  SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
32
32
  ```
33
+
34
+ ## Test cases from hoophq/fence — MIT
35
+
36
+ Some shell-command test cases in this project's tests (`test/core/shell-safety.test.ts` and `test/core/shell-safety-3.test.ts`, for example the recursive-delete commands and the expected block/allow outcomes) are taken from the test suite of hoophq/fence, https://github.com/hoophq/fence (`internal/analyzer/shell/shell_test.go`, commit 31623d48220f8b4abba67f4f9993884e45cd755c). The device-name pattern of `isBlockDevice` in `src/core/rules.ts` (which names count as raw disks) follows `blockDeviceRe` in fence's `internal/analyzer/shell/shell.go`, and the `$TMPDIR` handling follows the behavior its `TestTmpdirResolution` pins. No other fence code is included. The following is its upstream license and copyright notice:
37
+
38
+ ```text
39
+ MIT License
40
+
41
+ Copyright (c) 2026 hoop.dev
42
+
43
+ Permission is hereby granted, free of charge, to any person obtaining a copy
44
+ of this software and associated documentation files (the "Software"), to deal
45
+ in the Software without restriction, including without limitation the rights
46
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
47
+ copies of the Software, and to permit persons to whom the Software is
48
+ furnished to do so, subject to the following conditions:
49
+
50
+ The above copyright notice and this permission notice shall be included in all
51
+ copies or substantial portions of the Software.
52
+
53
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
54
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
55
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
56
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
57
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
58
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
59
+ SOFTWARE.
60
+ ```