@solongate/proxy 0.49.0 → 0.50.0
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 +72 -72
- package/dist/audit/index.js +0 -0
- package/dist/index.js +79 -782
- package/dist/login.js +2 -3
- package/hooks/audit.mjs +379 -293
- package/hooks/guard.bundled.mjs +7740 -7738
- package/hooks/guard.mjs +3 -1
- package/hooks/stop.mjs +75 -75
- package/package.json +76 -80
- package/dist/init.d.ts +0 -18
- package/dist/init.js +0 -910
package/README.md
CHANGED
|
@@ -1,72 +1,72 @@
|
|
|
1
|
-
# @solongate/proxy
|
|
2
|
-
|
|
3
|
-
> **Don't `npm i` this.** There's nothing to install. Run the two commands below to pair your machine:
|
|
4
|
-
> ```bash
|
|
5
|
-
> npx -y @solongate/proxy@latest
|
|
6
|
-
> npx -y @solongate/proxy@latest login
|
|
7
|
-
> ```
|
|
8
|
-
|
|
9
|
-
**Security for AI agents.** SolonGate enforces a security policy on every action an AI agent takes — every tool call is allowed, blocked, or logged before it runs. No code changes.
|
|
10
|
-
|
|
11
|
-
```
|
|
12
|
-
AI agent ──(tool call)──> SolonGate guard ──> Tool runs
|
|
13
|
-
│
|
|
14
|
-
[policy eval] ← OPA-WASM, fail-closed
|
|
15
|
-
[prompt-injection scan]
|
|
16
|
-
[allow / block / audit]
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
SolonGate comes in two editions that share the same policy model and dashboard:
|
|
20
|
-
|
|
21
|
-
- **Cloud** — managed, nothing to host. Pair your machine with one command and manage policies + audit logs at [dashboard.solongate.com](https://dashboard.solongate.com).
|
|
22
|
-
- **Local / air-gapped** — run the whole stack on your own hardware with Docker, zero outbound connectivity, no API keys.
|
|
23
|
-
|
|
24
|
-
---
|
|
25
|
-
|
|
26
|
-
## Quick start (Cloud)
|
|
27
|
-
|
|
28
|
-
**You need:** a free [SolonGate account](https://auth.solongate.com), Node.js 18+ on the machine you want to protect, and an AI tool that makes tool calls (Claude Code; Gemini CLI is also supported).
|
|
29
|
-
|
|
30
|
-
Pair the machine and turn on the guard — no API keys to copy. First fetch SolonGate, then log in:
|
|
31
|
-
|
|
32
|
-
```bash
|
|
33
|
-
npx -y @solongate/proxy@latest
|
|
34
|
-
npx -y @solongate/proxy@latest login
|
|
35
|
-
```
|
|
36
|
-
|
|
37
|
-
It opens your browser to authorize the device. Approve it from your signed-in dashboard and SolonGate installs a **global guard hook** that intercepts every tool call from every AI session on the machine and evaluates it against your active policy.
|
|
38
|
-
|
|
39
|
-
> Start a **new** terminal session afterwards — hooks load when a session starts, so already-open terminals aren't guarded yet.
|
|
40
|
-
|
|
41
|
-
## Write a policy
|
|
42
|
-
|
|
43
|
-
Open **Policies** in the dashboard and create one. A policy is a set of rules; each rule targets a tool plus a constraint (path / command / filename / URL) and is either ALLOW or DENY. Two modes:
|
|
44
|
-
|
|
45
|
-
- **Denylist** — everything is allowed except what you block (e.g. deny any file named `*.env`, or commands matching `*rm -rf*`).
|
|
46
|
-
- **Whitelist** — nothing is allowed except what you permit.
|
|
47
|
-
|
|
48
|
-
Click **Activate** to make a policy the one the guard enforces. Rules compile to an OPA-WASM bundle and take effect on the next tool call.
|
|
49
|
-
|
|
50
|
-
## Review the audit log
|
|
51
|
-
|
|
52
|
-
Every decision shows up under **Audit** — what was allowed, what was blocked, and which rule matched. When a legitimate action is blocked, open the entry and click **Whitelist this**: SolonGate adds a narrow ALLOW exception for exactly that action and recompiles. Revoke any exception from **Granted exceptions**.
|
|
53
|
-
|
|
54
|
-
## Uninstall
|
|
55
|
-
|
|
56
|
-
```bash
|
|
57
|
-
npx @solongate/proxy
|
|
58
|
-
```
|
|
59
|
-
|
|
60
|
-
---
|
|
61
|
-
|
|
62
|
-
## Why SolonGate?
|
|
63
|
-
|
|
64
|
-
AI agents get direct access to your system — shell, file system, databases, network. A single prompt-injection attack can turn your assistant into an attacker. SolonGate sits between the agent and the action, enforcing your policy on every tool call before it runs, and recording every decision for audit.
|
|
65
|
-
|
|
66
|
-
- **Docs:** [solongate.com/docs](https://solongate.com/docs)
|
|
67
|
-
- **Dashboard:** [dashboard.solongate.com](https://dashboard.solongate.com)
|
|
68
|
-
- **Air-gapped guide:** [solongate.com/docs/local](https://solongate.com/docs/local)
|
|
69
|
-
|
|
70
|
-
## License
|
|
71
|
-
|
|
72
|
-
MIT
|
|
1
|
+
# @solongate/proxy
|
|
2
|
+
|
|
3
|
+
> **Don't `npm i` this.** There's nothing to install. Run the two commands below to pair your machine:
|
|
4
|
+
> ```bash
|
|
5
|
+
> npx -y @solongate/proxy@latest
|
|
6
|
+
> npx -y @solongate/proxy@latest login
|
|
7
|
+
> ```
|
|
8
|
+
|
|
9
|
+
**Security for AI agents.** SolonGate enforces a security policy on every action an AI agent takes — every tool call is allowed, blocked, or logged before it runs. No code changes.
|
|
10
|
+
|
|
11
|
+
```
|
|
12
|
+
AI agent ──(tool call)──> SolonGate guard ──> Tool runs
|
|
13
|
+
│
|
|
14
|
+
[policy eval] ← OPA-WASM, fail-closed
|
|
15
|
+
[prompt-injection scan]
|
|
16
|
+
[allow / block / audit]
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
SolonGate comes in two editions that share the same policy model and dashboard:
|
|
20
|
+
|
|
21
|
+
- **Cloud** — managed, nothing to host. Pair your machine with one command and manage policies + audit logs at [dashboard.solongate.com](https://dashboard.solongate.com).
|
|
22
|
+
- **Local / air-gapped** — run the whole stack on your own hardware with Docker, zero outbound connectivity, no API keys.
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## Quick start (Cloud)
|
|
27
|
+
|
|
28
|
+
**You need:** a free [SolonGate account](https://auth.solongate.com), Node.js 18+ on the machine you want to protect, and an AI tool that makes tool calls (Claude Code; Gemini CLI is also supported).
|
|
29
|
+
|
|
30
|
+
Pair the machine and turn on the guard — no API keys to copy. First fetch SolonGate, then log in:
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
npx -y @solongate/proxy@latest
|
|
34
|
+
npx -y @solongate/proxy@latest login
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
It opens your browser to authorize the device. Approve it from your signed-in dashboard and SolonGate installs a **global guard hook** that intercepts every tool call from every AI session on the machine and evaluates it against your active policy.
|
|
38
|
+
|
|
39
|
+
> Start a **new** terminal session afterwards — hooks load when a session starts, so already-open terminals aren't guarded yet.
|
|
40
|
+
|
|
41
|
+
## Write a policy
|
|
42
|
+
|
|
43
|
+
Open **Policies** in the dashboard and create one. A policy is a set of rules; each rule targets a tool plus a constraint (path / command / filename / URL) and is either ALLOW or DENY. Two modes:
|
|
44
|
+
|
|
45
|
+
- **Denylist** — everything is allowed except what you block (e.g. deny any file named `*.env`, or commands matching `*rm -rf*`).
|
|
46
|
+
- **Whitelist** — nothing is allowed except what you permit.
|
|
47
|
+
|
|
48
|
+
Click **Activate** to make a policy the one the guard enforces. Rules compile to an OPA-WASM bundle and take effect on the next tool call.
|
|
49
|
+
|
|
50
|
+
## Review the audit log
|
|
51
|
+
|
|
52
|
+
Every decision shows up under **Audit** — what was allowed, what was blocked, and which rule matched. When a legitimate action is blocked, open the entry and click **Whitelist this**: SolonGate adds a narrow ALLOW exception for exactly that action and recompiles. Revoke any exception from **Granted exceptions**.
|
|
53
|
+
|
|
54
|
+
## Uninstall
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
npx @solongate/proxy logout
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## Why SolonGate?
|
|
63
|
+
|
|
64
|
+
AI agents get direct access to your system — shell, file system, databases, network. A single prompt-injection attack can turn your assistant into an attacker. SolonGate sits between the agent and the action, enforcing your policy on every tool call before it runs, and recording every decision for audit.
|
|
65
|
+
|
|
66
|
+
- **Docs:** [solongate.com/docs](https://solongate.com/docs)
|
|
67
|
+
- **Dashboard:** [dashboard.solongate.com](https://dashboard.solongate.com)
|
|
68
|
+
- **Air-gapped guide:** [solongate.com/docs/local](https://solongate.com/docs/local)
|
|
69
|
+
|
|
70
|
+
## License
|
|
71
|
+
|
|
72
|
+
MIT
|
package/dist/audit/index.js
CHANGED
|
File without changes
|