pure nodejs OPCUA SDK - module address-space
75%
Total Score
healthy
Active releases and repository work are offset by fully unpinned CI actions and a repository/package README mismatch.
The package declares 37 runtime dependencies, many from the same node-opcua family. This is a substantial dependency surface, but it is coherent with the package's broad address-space functionality.
The repository name does not match the package name and its README does not mention this package. Although a monorepo can explain the name mismatch, the lack of a README mention leaves some uncertainty that this repository directly represents the package.
The project uses established build tools, but no security-scanning tools were detected. The missing scanning layer is a modest transparency and hygiene concern.
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 documentation and publishing workflows. No untrusted checkout or script-injection trigger was reported, limiting the severity to workflow hygiene risk.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2024-10464 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. node-opcua-address-space is vulnerable to Prototype Pollution in versions 0.0.1 - 2.136.0. | 0.0.1 - 2.136.0 | Low |
| Dependency | Last Release | Score |
|---|---|---|
chalk Version 6.0.1 | — | — |
semver Version ^7.8.5 | — | — |
dequeue Version ^1.0.5 | — | — |
thenify-ex Version 4.4.0 | — | — |
xml-writer Version ^1.7.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.