@solongate/guard-win32-arm64 0.83.21
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 +13 -0
- package/package.json +21 -0
- package/solongate-guard.exe +0 -0
- package/solongate.exe +0 -0
package/README.md
ADDED
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# @solongate/guard-win32-arm64
|
|
2
|
+
|
|
3
|
+
Prebuilt SolonGate binaries for `win32`/`arm64`.
|
|
4
|
+
|
|
5
|
+
Installed automatically as an optional dependency of
|
|
6
|
+
[`@solongate/proxy`](https://www.npmjs.com/package/@solongate/proxy). There is no
|
|
7
|
+
reason to depend on it directly, and nothing in it to import: it contains two
|
|
8
|
+
executables and this file.
|
|
9
|
+
|
|
10
|
+
If npm skipped it — an unsupported platform, `--no-optional`, a restricted
|
|
11
|
+
registry — SolonGate still works. The guard falls back to its Node
|
|
12
|
+
implementation, which enforces the same policy more slowly. A missing binary
|
|
13
|
+
costs speed and never protection.
|
package/package.json
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@solongate/guard-win32-arm64",
|
|
3
|
+
"version": "0.83.21",
|
|
4
|
+
"description": "SolonGate guard and CLI binaries for win32-arm64",
|
|
5
|
+
"license": "MIT",
|
|
6
|
+
"repository": {
|
|
7
|
+
"type": "git",
|
|
8
|
+
"url": "https://github.com/solongate/solongate"
|
|
9
|
+
},
|
|
10
|
+
"os": [
|
|
11
|
+
"win32"
|
|
12
|
+
],
|
|
13
|
+
"cpu": [
|
|
14
|
+
"arm64"
|
|
15
|
+
],
|
|
16
|
+
"files": [
|
|
17
|
+
"solongate-guard.exe",
|
|
18
|
+
"solongate.exe"
|
|
19
|
+
],
|
|
20
|
+
"preferUnplugged": true
|
|
21
|
+
}
|
|
Binary file
|
package/solongate.exe
ADDED
|
Binary file
|