nxtsecure-openclaw 0.1.2 → 0.1.3

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
@@ -88,8 +88,8 @@ This repository is configured for npm trusted publishing with GitHub Actions.
88
88
  4. Create and push a matching git tag:
89
89
 
90
90
  ```bash
91
- git tag v0.1.2
92
- git push origin v0.1.2
91
+ git tag v0.1.3
92
+ git push origin v0.1.3
93
93
  ```
94
94
 
95
95
  Pushing a `v*` tag triggers `.github/workflows/publish.yml`, which publishes the package to npm using OIDC.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "nxtsecure-openclaw",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "npm CLI wrapper for the OpenClaw security audit skill",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -13,12 +13,16 @@ Use this skill when the user wants a repeatable OpenClaw host security audit, a
13
13
 
14
14
  ## Workflow
15
15
 
16
- 1. Prefer the npm CLI in `{baseDir}/../../bin/nxtsecure.mjs` to keep the agent workflow stable.
17
- 2. From the repository root, create the local configuration with `npm run nxtsecure -- openclaw config init --output ./openclaw-security-audit.conf` or copy `{baseDir}/references/openclaw-security-audit.conf.example`.
18
- 3. Run `npm run nxtsecure -- openclaw audit --config ./openclaw-security-audit.conf` to execute the audit and remediation workflow.
19
- 4. Install the nightly 23:00 cron entry with `npm run nxtsecure -- openclaw cron install --log ~/openclaw-security-audit.log`.
20
- 5. If every check passes, print exactly `audit de sécurité réussi`.
21
- 6. If a check fails, explain the issue, attempt remediation immediately, and rerun the relevant verification.
16
+ 1. First install or verify the CLI so the agent uses a stable interface:
17
+ `npm install -g nxtsecure-openclaw`
18
+ then verify with:
19
+ `nxtsecure openclaw doctor`
20
+ 2. If the CLI cannot be installed globally, fall back to the repository copy in `{baseDir}/../../bin/nxtsecure.mjs`.
21
+ 3. From the repository root, create the local configuration with `nxtsecure openclaw config init --output ./openclaw-security-audit.conf` or copy `{baseDir}/references/openclaw-security-audit.conf.example`.
22
+ 4. Run `nxtsecure openclaw audit --config ./openclaw-security-audit.conf` to execute the audit and remediation workflow.
23
+ 5. Install the nightly 23:00 cron entry with `nxtsecure openclaw cron install --log ~/openclaw-security-audit.log`.
24
+ 6. If every check passes, print exactly `audit de sécurité réussi`.
25
+ 7. If a check fails, explain the issue, attempt remediation immediately, and rerun the relevant verification.
22
26
 
23
27
  ## Checks
24
28
 
@@ -70,8 +74,8 @@ When the user wants file or link reputation checks, the agent must use VirusTota
70
74
 
71
75
  Use the bundled helper:
72
76
 
73
- - `npm run nxtsecure -- openclaw vt url https://example.test`
74
- - `npm run nxtsecure -- openclaw vt file /path/to/sample.bin`
77
+ - `nxtsecure openclaw vt url https://example.test`
78
+ - `nxtsecure openclaw vt file /path/to/sample.bin`
75
79
  - fallback: `{baseDir}/scripts/openclaw_virustotal_check.sh --url https://example.test`
76
80
  - fallback: `{baseDir}/scripts/openclaw_virustotal_check.sh --file /path/to/sample.bin`
77
81