node-opcua-pki 6.18.0 → 6.19.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/dist/bin/pki.mjs +1 -1
- package/dist/bin/pki.mjs.map +1 -1
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +1 -1
- package/dist/index.mjs.map +1 -1
- package/package.json +16 -8
- package/readme.md +34 -13
package/package.json
CHANGED
|
@@ -1,16 +1,24 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "node-opcua-pki",
|
|
3
|
-
"version": "6.
|
|
3
|
+
"version": "6.19.0",
|
|
4
4
|
"description": "PKI management for node-opcua",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"main": "./dist/index.js",
|
|
7
7
|
"types": "./dist/index.d.ts",
|
|
8
|
+
"//main": "main/types are the pre-'exports' fallback, used only by resolvers that ignore the exports map. They are deliberately left as the CommonJS pair, matching \"type\": \"commonjs\", so that path behaves exactly as it did before - do not 'fix' one without the other.",
|
|
9
|
+
"//exports": "types are declared PER CONDITION on purpose. A single shared \"types\" key is resolved for BOTH import and require; since this package is \"type\": \"commonjs\", a bare .d.ts is a CommonJS module, so an ESM consumer got CJS types describing the real .mjs it imports. attw reports that as FalseCJS ('Masquerading as CJS'); it was present in 6.18.0. The .d.mts file already existed - tsup emits it from dts:true with format esm+cjs - the map simply never pointed at it.",
|
|
8
10
|
"exports": {
|
|
9
11
|
".": {
|
|
10
|
-
"
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
12
|
+
"import": {
|
|
13
|
+
"types": "./dist/index.d.mts",
|
|
14
|
+
"default": "./dist/index.mjs"
|
|
15
|
+
},
|
|
16
|
+
"require": {
|
|
17
|
+
"types": "./dist/index.d.ts",
|
|
18
|
+
"default": "./dist/index.js"
|
|
19
|
+
}
|
|
20
|
+
},
|
|
21
|
+
"./package.json": "./package.json"
|
|
14
22
|
},
|
|
15
23
|
"bin": {
|
|
16
24
|
"pki": "./dist/bin/pki.mjs",
|
|
@@ -45,8 +53,8 @@
|
|
|
45
53
|
"chokidar": "4.0.3",
|
|
46
54
|
"command-line-args": "^6.0.2",
|
|
47
55
|
"command-line-usage": "^7.0.4",
|
|
48
|
-
"node-opcua-crypto": "5.
|
|
49
|
-
"yauzl": "^3.
|
|
56
|
+
"node-opcua-crypto": "5.4.0",
|
|
57
|
+
"yauzl": "^3.4.0"
|
|
50
58
|
},
|
|
51
|
-
"gitHead": "
|
|
59
|
+
"gitHead": "3a43116bac242fa14bdc99ae1bdee1f4054fdb6b"
|
|
52
60
|
}
|
package/readme.md
CHANGED
|
@@ -4,7 +4,15 @@
|
|
|
4
4
|
[](https://www.npmjs.com/package/node-opcua-pki?activeTab=versions)
|
|
5
5
|
[](https://packagephobia.com/result?p=node-opcua-pki)
|
|
6
6
|
|
|
7
|
-
**PKI management for [
|
|
7
|
+
**Production-grade PKI management for [OPC UA](https://node-opcua.github.io/)** — secure your industrial devices with proper certificates in minutes, not days.
|
|
8
|
+
|
|
9
|
+
## Why node-opcua-pki?
|
|
10
|
+
|
|
11
|
+
- 🔒 **OPC UA compliant** — PKI directory structure per Part 6 §6.2.6, out of the box
|
|
12
|
+
- 🏗️ **Full CA lifecycle** — create, sign, revoke, renew certificates and CRLs
|
|
13
|
+
- 🖥️ **Cross-platform** — Windows, Linux, macOS, Alpine, with automatic OpenSSL detection
|
|
14
|
+
- 🧩 **CLI + API** — use from the command line or embed in your Node.js application
|
|
15
|
+
- 🛡️ **Battle-tested** — 12 years of continuous development, powering production OPC UA deployments worldwide
|
|
8
16
|
|
|
9
17
|
## Quick Start
|
|
10
18
|
|
|
@@ -23,12 +31,31 @@ pki --help
|
|
|
23
31
|
|
|
24
32
|
This module requires **OpenSSL** or **LibreSSL**:
|
|
25
33
|
|
|
26
|
-
| Platform | Installation
|
|
27
|
-
| ----------------- |
|
|
28
|
-
| **Windows** |
|
|
29
|
-
| **Ubuntu/Debian** | `apt install openssl`
|
|
30
|
-
| **Alpine** | `apk add openssl`
|
|
31
|
-
| **macOS** | Pre-installed (LibreSSL)
|
|
34
|
+
| Platform | Installation |
|
|
35
|
+
| ----------------- | ------------------------------------------------------ |
|
|
36
|
+
| **Windows** | Auto-detected from system PATH, or downloaded on first run |
|
|
37
|
+
| **Ubuntu/Debian** | `apt install openssl` |
|
|
38
|
+
| **Alpine** | `apk add openssl` |
|
|
39
|
+
| **macOS** | Pre-installed (LibreSSL) |
|
|
40
|
+
|
|
41
|
+
## 🏢 Professional Support
|
|
42
|
+
|
|
43
|
+
node-opcua-pki is developed and maintained by [Sterfive](https://www.sterfive.com), the company behind the [node-opcua](https://github.com/node-opcua/node-opcua) ecosystem.
|
|
44
|
+
|
|
45
|
+
| | Community | Professional |
|
|
46
|
+
|---|:---:|:---:|
|
|
47
|
+
| Full documentation & CLI | ✅ | ✅ |
|
|
48
|
+
| Bug fixes & security patches | Best effort | **Priority SLA** |
|
|
49
|
+
| Security advisories | Public | **Early access** |
|
|
50
|
+
| Custom certificate workflows | — | ✅ |
|
|
51
|
+
| Dedicated consulting | — | ✅ |
|
|
52
|
+
| PKI architecture review | — | ✅ |
|
|
53
|
+
|
|
54
|
+
[](https://support.sterfive.com)
|
|
55
|
+
|
|
56
|
+
Or [contact Sterfive](mailto:contact@sterfive.com) for dedicated consulting and enterprise needs.
|
|
57
|
+
|
|
58
|
+
---
|
|
32
59
|
|
|
33
60
|
## CLI Commands
|
|
34
61
|
|
|
@@ -238,12 +265,6 @@ await intCA.installCACertificate(certFile); // Step 3
|
|
|
238
265
|
- [RFC 5280 — X.509 PKI Certificate and CRL Profile](https://tools.ietf.org/html/rfc5280)
|
|
239
266
|
- [Certification Path Validation](https://en.wikipedia.org/wiki/Certification_path_validation_algorithm)
|
|
240
267
|
|
|
241
|
-
## Support
|
|
242
|
-
|
|
243
|
-
NodeOPCUA PKI is developed and maintained by [sterfive.com](https://www.sterfive.com).
|
|
244
|
-
|
|
245
|
-
[](https://support.sterfive.com)
|
|
246
|
-
|
|
247
268
|
## License
|
|
248
269
|
|
|
249
270
|
MIT — Copyright (c) 2014-2026 Etienne Rossignon / [Sterfive](https://www.sterfive.com)
|