@quantumsequrity/qnsqy-linux-arm64 0.0.0-stage → 7.2.48

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/LICENSE ADDED
@@ -0,0 +1,15 @@
1
+ QNSQY PROPRIETARY LICENSE
2
+
3
+ Copyright (c) 2026 Quantum Sequrity. All rights reserved.
4
+
5
+ 1. This package contains the prebuilt QNSQY binary for Linux ARM64 (aarch64),
6
+ licensed under the QNSQY end-user license agreement:
7
+ https://quantumsequrity.com/terms
8
+
9
+ 2. This package exists solely as an optional dependency of the qnsqy npm
10
+ package, to deliver the platform binary. You may use it only through
11
+ that channel, to install and run the official QNSQY binary. No other
12
+ rights are granted.
13
+
14
+ 3. Source access for security audit is available on request:
15
+ security@quantumsequrity.com
package/README.md CHANGED
@@ -1,3 +1,122 @@
1
- # Temporary Holding Version
1
+ # @quantumsequrity/qnsqy-linux-arm64
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Prebuilt [QNSQY](https://www.npmjs.com/package/qnsqy) binary for **Linux
4
+ ARM64 (aarch64)** (glibc 2.28+). QNSQY is a post-quantum cryptography tool built on
5
+ NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA),
6
+ with AES-256-GCM, pure post-quantum or hybridized with X25519 and Ed25519.
7
+
8
+ ## Do not install this package directly
9
+
10
+ This package only carries the platform binary. It is pulled in
11
+ automatically as an `optionalDependencies` entry of the main `qnsqy`
12
+ package, so `npm` downloads only the binary that matches your platform
13
+ (selected by the `os` / `cpu` fields). It contains **no install scripts
14
+ and makes no network calls** during installation.
15
+
16
+ Install the main package instead:
17
+
18
+ ```bash
19
+ npm install -g qnsqy
20
+ qnsqy --help
21
+ ```
22
+
23
+ ## What the binary does
24
+
25
+ One executable, four run modes: command line (`qnsqy`), terminal UI
26
+ (`qnsqy --tui`), desktop GUI (`qnsqy --gui`), and an MCP server for AI
27
+ agents (`qnsqy --mcp`, 84 tools). Core operations:
28
+
29
+ - **Encrypt / decrypt** with hybrid post-quantum envelopes: ML-KEM
30
+ (512/768/1024) combined with X25519, sealed with AES-256-GCM or
31
+ XChaCha20-Poly1305, passwords stretched with Argon2id.
32
+ - **Sign / verify** with ML-DSA (44/65/87) combined with Ed25519, plus
33
+ SLH-DSA, FN-DSA, and LMS / HSS (SP 800-208) on higher tiers.
34
+ - **Hash / verify-integrity** with BLAKE3, SHA-2, and SHA-3.
35
+ - **Key tools**: keygen, key import/export, password vault,
36
+ multi-recipient encryption, M-of-N threshold encryption, Shamir secret
37
+ sharing, key escrow, time-lock encryption.
38
+ - **Migration**: scan data for legacy classical cryptography and
39
+ re-encrypt it under post-quantum algorithms.
40
+ - **Audit logging** with hash-chained entries and SIEM/CSV/JSON export.
41
+
42
+ All cryptographic operations run locally. Plaintext, passwords, and
43
+ private keys never leave the machine.
44
+
45
+ ## Linux-specific hardening
46
+
47
+ The Linux build carries the strongest sandbox in the product line:
48
+
49
+ - **seccomp-bpf network drop**: after subscription authorization, a
50
+ one-way kernel filter permanently removes network access before any
51
+ cryptographic operation touches plaintext or keys.
52
+ - **Landlock** filesystem scoping restricts which paths the process can
53
+ reach.
54
+ - **Memory hygiene**: mlock(2) to keep secrets out of swap, zeroization
55
+ of key material, core dumps disabled.
56
+
57
+ ## Integrity model (defense in depth)
58
+
59
+ 1. **npm shim pinning.** The main `qnsqy` package ships
60
+ `bin/integrity.json` with the SHA-256 of this binary. The shim
61
+ verifies the hash before every run and refuses to execute a
62
+ substituted or tampered binary.
63
+ 2. **Startup self-check.** The binary verifies its own embedded
64
+ integrity hash at startup.
65
+ 3. **Release manifest signature.** The same bytes are published on the
66
+ download page and listed in `checksums.txt`, which is signed with an
67
+ **ML-DSA-87 (FIPS 204, security category 5)** post-quantum signature
68
+ made with an offline release key. Verify with any QNSQY install:
69
+ `qnsqy verify-release checksums.txt checksums.txt.sig`
70
+ 4. **Sigstore transparency log.** The release manifest is additionally
71
+ signed keylessly from the public GitHub repository's CI identity and
72
+ recorded in the Sigstore Rekor transparency log, so the release
73
+ history is publicly auditable.
74
+
75
+ Manual hash check:
76
+
77
+ ```bash
78
+ sha256sum node_modules/@quantumsequrity/qnsqy-linux-arm64/qnsqy
79
+ # Compare against the Linux checksum on https://quantumsequrity.com/download
80
+ ```
81
+
82
+ ## Supported platforms
83
+
84
+ | Target | Status |
85
+ |--------|--------|
86
+ | Linux x86_64, glibc 2.28+ (RHEL 8+ and its rebuilds, Amazon Linux 2023, Fedora 40+, Ubuntu 20.04+, Debian 11+, SLES 15 SP6) | use `@quantumsequrity/qnsqy-linux-x64` |
87
+ | Linux ARM64 (aarch64), glibc 2.28+ | supported (this package) |
88
+ | Windows 10 1809+ / 11 x86_64 | use `@quantumsequrity/qnsqy-win32-x64` |
89
+ | macOS | in development |
90
+
91
+ Native `.deb` / `.rpm` packages and signed repositories are also
92
+ available on the download page if you prefer the system package manager
93
+ over npm.
94
+
95
+ ## Troubleshooting
96
+
97
+ - **"integrity mismatch" from the shim**: the binary on disk does not
98
+ match the pinned SHA-256. Reinstall with
99
+ `npm install -g qnsqy --force`. If it persists, treat it as a
100
+ security signal and compare hashes against the download page.
101
+ - **glibc errors on old distributions**: the binary requires glibc 2.28
102
+ or newer. Check with `ldd --version`. Use a newer distribution.
103
+ - **Running a pre-staged binary** (air-gapped or mirrored installs): set
104
+ `QNSQY_BINARY_PATH` to an absolute path and the shim will verify and
105
+ run that binary instead of the packaged one.
106
+ - **Version note**: the npm package version can be ahead of the binary's
107
+ self-reported `qnsqy version` when a release only changes packaging.
108
+ The binary version is authoritative for cryptographic behavior.
109
+
110
+ ## Links
111
+
112
+ - Homepage: https://quantumsequrity.com
113
+ - Download page (checksums + post-quantum signatures): https://quantumsequrity.com/download
114
+ - Documentation: https://quantumsequrity.com/docs.html
115
+ - Wrapper source: https://github.com/quantumsequrity/qnsqy
116
+ - Issues: https://github.com/quantumsequrity/qnsqy/issues
117
+ - Security disclosure: security@quantumsequrity.com
118
+
119
+ ## License
120
+
121
+ Proprietary. (c) 2026 Quantum Sequrity. See the bundled `LICENSE`.
122
+ Source access for security audit is available on request.
package/SECURITY.md ADDED
@@ -0,0 +1,29 @@
1
+ # Security Policy
2
+
3
+ ## Supported Versions
4
+
5
+ We provide security updates for the latest stable release of QNSQY.
6
+
7
+ | Version | Supported |
8
+ | ------- | ------------------ |
9
+ | v7.2.x | :white_check_mark: |
10
+ | < v7.2 | :x: |
11
+
12
+ ## Reporting a Vulnerability
13
+
14
+ We take the security of QNSQY seriously. If you believe you have found a security vulnerability, please report it to us privately.
15
+
16
+ **Please do not open a public GitHub issue for security vulnerabilities.**
17
+
18
+ You can report vulnerabilities via:
19
+ - **Email:** security@quantumsequrity.com
20
+ - **Website:** https://quantumsequrity.com/contact
21
+
22
+ We will acknowledge receipt of your report within 48 hours and provide a timeline for remediation.
23
+
24
+ ## Our Security Model
25
+
26
+ QNSQY is built on NIST-standardized post-quantum algorithms (FIPS 203, 204, 205). Our security guarantees include:
27
+ - **Zero Telemetry:** Your data and keys never leave your machine.
28
+ - **Kernel Sandboxing:** (Linux only) Seccomp-BPF and Landlock enforced by default.
29
+ - **Memory Protection:** mlock(2) used to prevent secrets from being swapped to disk.
package/package.json CHANGED
@@ -1,6 +1,41 @@
1
1
  {
2
2
  "name": "@quantumsequrity/qnsqy-linux-arm64",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
3
+ "version": "7.2.48",
4
+ "description": "Prebuilt QNSQY binary for Linux ARM64 (aarch64). Installed automatically as an optional dependency of the `qnsqy` package. Do not install directly.",
5
+ "keywords": [
6
+ "qnsqy",
7
+ "post-quantum",
8
+ "cryptography",
9
+ "pqc",
10
+ "quantum-safe",
11
+ "prebuilt-binary",
12
+ "linux",
13
+ "arm64"
14
+ ],
15
+ "homepage": "https://quantumsequrity.com",
16
+ "repository": {
17
+ "type": "git",
18
+ "url": "git+https://github.com/quantumsequrity/qnsqy.git",
19
+ "directory": "platform-packages/qnsqy-linux-arm64"
20
+ },
21
+ "bugs": "https://github.com/quantumsequrity/qnsqy/issues",
22
+ "license": "SEE LICENSE IN LICENSE",
23
+ "author": "Quantum Sequrity",
24
+ "os": [
25
+ "linux"
26
+ ],
27
+ "cpu": [
28
+ "arm64"
29
+ ],
30
+ "engines": {
31
+ "node": ">=18.0.0"
32
+ },
33
+ "preferUnplugged": true,
34
+ "publishConfig": {
35
+ "access": "public"
36
+ },
37
+ "files": [
38
+ "qnsqy",
39
+ "SECURITY.md"
40
+ ]
41
+ }
package/qnsqy ADDED
@@ -0,0 +1,4 @@
1
+ [diffend] Oversized file quarantined before diffing.
2
+ name: package/qnsqy
3
+ size: 55614264 bytes
4
+ sha256: 2ca14792672b372a47f29a1da46b6b4b4a76d2879b43a16f1513e226491fa61c