@moxxy/plugin-channel-whatsapp 0.36.1 → 0.37.1
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/dist/auth-state.d.ts +1 -1
- package/package.json +11 -11
- package/src/auth-state.ts +1 -1
package/dist/auth-state.d.ts
CHANGED
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
* it (the vault is an encrypted, tagged, human-curated secret store, not a
|
|
8
8
|
* high-write key-value backend); instead the state lives in a dedicated
|
|
9
9
|
* directory under the moxxy home with tight modes (dir 0700, files 0600).
|
|
10
|
-
* TRADE-OFF
|
|
10
|
+
* TRADE-OFF: unlike vault entries, these files
|
|
11
11
|
* are NOT encrypted at rest — anyone with file access to the moxxy home can
|
|
12
12
|
* hijack the linked WhatsApp session. The {@link WhatsAppAuthStorage} interface
|
|
13
13
|
* exists precisely so an encrypted backend can be swapped in later without
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@moxxy/plugin-channel-whatsapp",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.37.1",
|
|
4
4
|
"description": "WhatsApp channel for moxxy via Baileys (UNOFFICIAL WhatsApp Web protocol — violates WhatsApp's Terms of Service; the linked number can be banned, use a secondary number). QR device-link pairing, JID allow-list, voice-note transcription, dedicated isolated runner.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"moxxy",
|
|
@@ -74,21 +74,21 @@
|
|
|
74
74
|
"@clack/prompts": "^1.4.0",
|
|
75
75
|
"@whiskeysockets/baileys": "^6.7.21",
|
|
76
76
|
"qrcode": "^1.5.4",
|
|
77
|
-
"zod": "^3.
|
|
78
|
-
"@moxxy/
|
|
79
|
-
"@moxxy/
|
|
80
|
-
"@moxxy/
|
|
81
|
-
"@moxxy/
|
|
77
|
+
"zod": "^3.25.76",
|
|
78
|
+
"@moxxy/core": "0.37.1",
|
|
79
|
+
"@moxxy/plugin-vault": "0.37.1",
|
|
80
|
+
"@moxxy/channel-kit": "0.37.1",
|
|
81
|
+
"@moxxy/sdk": "0.37.1"
|
|
82
82
|
},
|
|
83
83
|
"devDependencies": {
|
|
84
84
|
"@types/node": "^22.10.0",
|
|
85
85
|
"@types/qrcode": "^1.5.5",
|
|
86
86
|
"typescript": "^5.7.3",
|
|
87
|
-
"vitest": "^2.
|
|
88
|
-
"@moxxy/mode-default": "0.
|
|
89
|
-
"@moxxy/testing": "0.0.
|
|
90
|
-
"@moxxy/
|
|
91
|
-
"@moxxy/
|
|
87
|
+
"vitest": "^3.2.6",
|
|
88
|
+
"@moxxy/mode-default": "0.37.1",
|
|
89
|
+
"@moxxy/testing": "0.0.62",
|
|
90
|
+
"@moxxy/vitest-preset": "0.0.0",
|
|
91
|
+
"@moxxy/tsconfig": "0.0.0"
|
|
92
92
|
},
|
|
93
93
|
"scripts": {
|
|
94
94
|
"build": "tsc -p tsconfig.json",
|
package/src/auth-state.ts
CHANGED
|
@@ -10,7 +10,7 @@ import * as path from 'node:path';
|
|
|
10
10
|
* it (the vault is an encrypted, tagged, human-curated secret store, not a
|
|
11
11
|
* high-write key-value backend); instead the state lives in a dedicated
|
|
12
12
|
* directory under the moxxy home with tight modes (dir 0700, files 0600).
|
|
13
|
-
* TRADE-OFF
|
|
13
|
+
* TRADE-OFF: unlike vault entries, these files
|
|
14
14
|
* are NOT encrypted at rest — anyone with file access to the moxxy home can
|
|
15
15
|
* hijack the linked WhatsApp session. The {@link WhatsAppAuthStorage} interface
|
|
16
16
|
* exists precisely so an encrypted backend can be swapped in later without
|