View node-opcua-crypto on Snyk Open Source Advisor

Package Health Score

73 / 100

security
No known security issues
popularity
Recognized
maintenance
Healthy
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
4.15.0	\|	12/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.12.0	\|	10/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.8.0	\|	02/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.1.0	\|	07/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.2.0	\|	05/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (25,784)

GitHub Stars: 5
Forks: 10
Contributors: 7

Direct Usage Popularity

The npm package node-opcua-crypto receives a total of 25,784 downloads a week. As such, we scored node-opcua-crypto popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package node-opcua-crypto, we found that it has been starred 5 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: No
Contributing.md: No
Code of Conduct: No
Contributors: 7
Funding: Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like node-opcua-crypto is missing a Code of Conduct.

How about a good first contribution to this project? It seems that node-opcua-crypto is missing a README file.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 2
Open PR: 0
Last Release: 8 days ago
Last Commit: 8 days ago

Further analysis of the maintenance status of node-opcua-crypto based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that node-opcua-crypto demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 9 years
Dependencies: 9 Direct
Versions: 102
Install Size: 3.52 MB
Dist-tags: 2
# of Files: 35
Maintainers: 1
TS Typings: Yes

node-opcua-crypto has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use node-opcua-crypto?

To help you get started, we've collected the most common ways that node-opcua-crypto is being used within popular public projects.

node-opcua / node-opcua / packages / node-opcua-secure-channel / test_helpers / fake_message_chunk_factory.ts View on Github

encryptBufferWithDerivedKeys,
    makeMessageChunkSignature,
    makeMessageChunkSignatureWithDerivedKeys,
    makeSHA1Thumbprint,
    publicEncrypt_long,
    readCertificate,
    readKeyPem,
    RSA_PKCS1_PADDING
} from "node-opcua-crypto";
import { AsymmetricAlgorithmSecurityHeader, SymmetricAlgorithmSecurityHeader } from "node-opcua-service-secure-channel";
import { SecureMessageChunkManager, SequenceNumberGenerator } from "../source";

// tslint:disable:no-var-requires
const getFixture = require("node-opcua-test-fixtures").getFixture;

const senderCertificate = readCertificate(getFixture("certs/client_cert_1024.pem"));
const senderPrivateKey = readKeyPem(getFixture("certs/client_key_1024.pem"));

const receiverCertificate =  readCertificate(getFixture("certs/server_cert_1024.pem"));
const receiverCertificateThumbprint = makeSHA1Thumbprint(receiverCertificate);

const receiverPublicKey = fs.readFileSync(getFixture("certs/server_public_key_1024.pub", "ascii")).toString();

const sequenceNumberGenerator = new SequenceNumberGenerator();

export type ChunkVisitorFunc = (err: Error | null, chunk?: Buffer) => void;

export function iterateOnSignedMessageChunks(buffer: Buffer, callback: ChunkVisitorFunc) {

    const params = {
        algorithm: "RSA-SHA1",
        privateKey: senderPrivateKey,

View more ways to use node-opcua-crypto

node-opcua-crypto dependencies

@peculiar/webcrypto @peculiar/x509 @types/jsrsasign @types/sshpk assert chalk hexy jsrsasign sshpk

node-opcua-crypto development dependencies

@types/node lorem-ipsum

FAQs

What is node-opcua-crypto?

Crypto tools for Node-OPCUA. Visit Snyk Advisor to see a full health score report for node-opcua-crypto, including popularity, security, maintenance & community analysis.

Is node-opcua-crypto popular?

The npm package node-opcua-crypto receives a total of 25,784 weekly downloads. As such, node-opcua-crypto popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is node-opcua-crypto well maintained?

We found that node-opcua-crypto demonstrated a healthy version release cadence and project activity. It has a community of 7 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is node-opcua-crypto safe to use?

The npm package node-opcua-crypto was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 December-2024, at 00:02 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

node-opcua-crypto

Crypto tools for Node-OPCUA For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (25,784)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use node-opcua-crypto?

node-opcua-crypto dependencies

node-opcua-crypto development dependencies

FAQs

What is node-opcua-crypto?

Is node-opcua-crypto popular?

Is node-opcua-crypto well maintained?

Is node-opcua-crypto safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (25,784)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use node-opcua-crypto?

node-opcua-crypto dependencies

node-opcua-crypto development dependencies

FAQs

What is node-opcua-crypto?

Is node-opcua-crypto popular?

Is node-opcua-crypto well maintained?

Is node-opcua-crypto safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues