Gathering detailed insights and metrics for node-opcua-crypto
Gathering detailed insights and metrics for node-opcua-crypto
Gathering detailed insights and metrics for node-opcua-crypto
Gathering detailed insights and metrics for node-opcua-crypto
npm install node-opcua-crypto
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
5 Stars
348 Commits
10 Forks
4 Watching
22 Branches
6 Contributors
Updated on 13 Oct 2024
TypeScript (96.65%)
JavaScript (2.07%)
HTML (1.17%)
Makefile (0.11%)
Cumulative downloads
Total Downloads
Last day
3.9%
5,206
Compared to previous day
Last week
12.4%
27,253
Compared to previous week
Last month
-15.3%
112,920
Compared to previous month
Last year
9.3%
1,311,301
Compared to previous year
9
2
NodeOPCUA Crypto is a powerful JavaScript module for handling security and cryptography for OPCUA. It's written in TypeScript and runs smoothly on Node.js and in the browser.
To use NodeOPCUA Crypto in your project, follow these steps:
1npm install nodeopcua-crypto
1 2import { generatePrivateKey, privateKeyToPEM, CertificatePurpose, createSelfSignedCertificate } from "./node-opcua-crypto.js"; 3 4async function demonstratePrivateKeyAndSelfSignedCertificateCreation() { 5 6 // create the Private Key 7 const privateKey = await generatePrivateKey(); 8 9 // convert the private key to a PEM format 10 const { privPem } = await privateKeyToPEM(privateKey); 11 12 console.log(privPem); 13 14 // create a self-sign certificate 15 const { cert } = await createSelfSignedCertificate({ 16 privateKey, 17 notAfter: new Date(2025, 1, 1), 18 notBefore: new Date(2019, 1, 1), 19 subject: "CN=Test", 20 dns: ["DNS1", "DNS2"], 21 ip: ["192.168.1.1"], 22 applicationUri: "urn:HOSTNAME:ServerDescription", 23 purpose: CertificatePurpose.ForApplication, 24 }); 25 console.log(cert); 26} 27demonstratePrivateKeyAndSelfSignedCertificateCreation(); 28 29
Please refer to the examples directory for more specific use cases and comprehensive samples.
Sterfive provides this module free of charge, "as is," with the hope that it will be useful to you. However, any support requests, bug fixes, or enhancements are handled exclusively through our paid services. We believe strongly that independent open-source companies should be fairly compensated for their contributions to the community.
We highly recommend subscribing to our support program to ensure your requests are addressed and resolved. Please note that we only consider requests from members of our support program or sponsors.
NodeOPCUA Crypto is developed and maintained by sterfive.com.
To get professional support, consider subscribing to the node-opcua membership community:
or contact sterfive for dedicated consulting and more advanced support.
We appreciate contributions from the community. To contribute:
For more detailed instructions, refer to the CONTRIBUTING.md file.
NodeOPCUA Crypto is MIT licensed. See the LICENSE file for full license details.
Copyright © 2023-2024 Sterfive.com.
NodeOPCUA Crypto is provided as-is, and while we strive to ensure its quality and security, Sterfive.com cannot be held liable for any damage caused directly or indirectly by the usage of this module.
Please report any issues or vulnerabilities you find via the issue tracker.
Thank you for considering NodeOPCUA Crypto for your OPCUA cryptography needs. We look forward to seeing what you build with i
If you like node-opcua-crypto
and if you are relying on it in one of your projects, please consider becoming a backer and sponsoring us, this will help us to maintain a high-quality stack and constant evolution of this module.
If your company would like to participate and influence the development of future versions of node-opcua
and its components, please contact sterfive.
No vulnerabilities found.
Reason
17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
2 existing vulnerabilities detected
Details
Reason
Found 0/25 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More