pure nodejs OPCUA SDK - module secure-channel
78%
Total Score
healthy
Frequent releases and active organization backing support this stable release despite workflow and package-identity gaps.
The repository name does not match this package and its README does not mention it, creating some uncertainty about package-to-repository identity; the organization repository context partly offsets that concern for a monorepo subpackage.
The project uses Make, TypeScript, npm scripts, and tsup, but no security scanning tools were detected; the missing scanning is a modest hygiene gap.
All three workflows were analyzed, but all 32 action references are unpinned, one workflow grants top-level write permissions, and high-confidence template-injection findings appear in docs and publish workflows. The low-confidence cache-poisoning finding is hygiene only, while no untrusted checkout or script-injection trigger was found.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-10340 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. node-opcua-secure-channel is vulnerable to Race condition in versions 0.0.1 - 2.164.1. | 0.0.1 - 2.164.1 | Low |
| Dependency | Last Release | Score |
|---|---|---|
chalk Version 6.0.1 | — | — |
backoff Version ^2.5.0 | — | — |
node-opcua-debug Version 2.186.7 | — | — |
node-opcua-types Version 2.187.0 | — | — |
node-opcua-utils Version 2.187.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.