node-opcua-client
pure nodejs OPCUA SDK - module client
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:underscore | AI (phantom-deps): Common utility lib, likely used in compiled dist not scanned source. | ai | |
| phantom-deps | phantom-dep:delayed | AI (phantom-deps): Runtime util used indirectly; heuristic false positive for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Generates local self-signed cert via node-opcua-pki; documented, stable across versions. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from erossignon to GitHub Actions CI/CD publishing; backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; SLSA attestation confirms legitimate publish. | ai | |
| bogus-package | bogus-package | AI (bogus-package): node-opcua monorepo legitimately produces 100+ same-named packages; not spam or phishing. | ai |
Versions (showing 100 of 219)
| Version | Deps | Published |
|---|---|---|
| 2.90.0 | 46 / 11 | |
| 2.89.0 | 46 / 11 | |
| 2.88.0 | 46 / 11 | |
| 2.87.0 | 46 / 11 | |
| 2.86.1 | 46 / 11 | |
| 2.86.0 | 46 / 11 | |
| 2.85.0 | 46 / 11 | |
| 2.84.0 | 46 / 11 | |
| 2.83.0 | 46 / 11 | |
| 2.82.0 | 46 / 11 | |
| 2.81.0 | 46 / 11 | |
| 2.80.0 | 46 / 11 | |
| 2.79.1 | 46 / 11 | |
| 2.79.0 | 46 / 11 | |
| 2.78.0 | 46 / 11 | |
| 2.77.0 | 46 / 11 | |
| 2.76.2 | 46 / 11 | |
| 2.76.1 | 46 / 11 | |
| 2.76.0 | 46 / 11 | |
| 2.74.0 | 49 / 8 | |
| 2.73.1 | 49 / 8 | |
| 2.73.0 | 49 / 8 | |
| 2.72.2 | 49 / 8 | |
| 2.72.1 | 49 / 8 | |
| 2.72.0 | 49 / 8 | |
| 2.70.3 | 49 / 8 | |
| 2.70.2 | 49 / 8 | |
| 2.70.1 | 49 / 8 | |
| 2.70.0 | 49 / 8 | |
| 2.69.1 | 49 / 8 | |
| 2.69.0 | 49 / 8 | |
| 2.68.1 | 49 / 8 | |
| 2.67.0 | 49 / 8 | |
| 2.66.3 | 49 / 8 | |
| 2.66.0 | 49 / 8 | |
| 2.65.1 | 49 / 8 | |
| 2.65.0 | 49 / 8 | |
| 2.64.1 | 49 / 8 | |
| 2.64.0 | 49 / 8 | |
| 2.63.2 | 49 / 8 | |
| 2.63.1 | 49 / 8 | |
| 2.63.0 | 49 / 8 | |
| 2.62.4 | 49 / 8 | |
| 2.62.3 | 49 / 8 | |
| 2.62.2 | 49 / 8 | |
| 2.62.1 | 49 / 8 | |
| 2.62.0 | 49 / 8 | |
| 2.61.0 | 49 / 8 | |
| 2.60.0 | 49 / 8 | |
| 2.59.0 | 49 / 8 | |
| 2.58.0 | 49 / 8 | |
| 2.57.0 | 49 / 8 | |
| 2.56.3 | 49 / 8 | |
| 2.56.0 | 49 / 8 | |
| 2.55.0 | 49 / 8 | |
| 2.53.0 | 49 / 8 | |
| 2.52.0 | 49 / 8 | |
| 2.50.0 | 49 / 8 | |
| 2.49.0 | 49 / 8 | |
| 2.48.0 | 49 / 8 | |
| 2.47.0 | 49 / 8 | |
| 2.43.0 | 49 / 8 | |
| 2.42.0 | 49 / 8 | |
| 2.41.0 | 49 / 8 | |
| 2.40.0 | 49 / 8 | |
| 2.37.0 | 48 / 8 | |
| 2.36.0 | 48 / 8 | |
| 2.35.0 | 48 / 8 | |
| 2.34.0 | 48 / 8 | |
| 2.33.0 | 48 / 8 | |
| 2.32.0 | 48 / 8 | |
| 2.31.0 | 48 / 8 | |
| 2.29.0 | 48 / 8 | |
| 2.28.2 | 48 / 8 | |
| 2.28.1 | 48 / 8 | |
| 2.28.0 | 48 / 8 | |
| 2.27.1 | 48 / 8 | |
| 2.27.0 | 48 / 8 | |
| 2.25.0 | 48 / 8 | |
| 2.24.1 | 48 / 8 | |
| 2.24.0 | 48 / 8 | |
| 2.23.0 | 48 / 8 | |
| 2.22.0 | 48 / 8 | |
| 2.21.0 | 48 / 8 | |
| 2.20.0 | 48 / 8 | |
| 2.19.0 | 48 / 8 | |
| 2.17.0 | 48 / 8 | |
| 2.16.0 | 48 / 8 | |
| 2.15.0 | 48 / 8 | |
| 2.12.0 | 48 / 8 | |
| 2.11.0 | 48 / 8 | |
| 2.10.0 | 48 / 8 | |
| 2.9.1 | 48 / 9 | |
| 2.9.0 | 48 / 9 | |
| 2.8.0 | 49 / 9 | |
| 2.6.7 | 49 / 9 | |
| 2.6.6 | 49 / 9 | |
| 2.6.5 | 49 / 9 | |
| 2.6.4 | 49 / 9 | |
| 2.6.3 | 49 / 9 |
v2.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.76.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.76.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.2
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.1
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.1
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.1
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.7
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.6
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.5
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.3
2 findingsScript: node test_helpers/create_certificates.js certificate -s -o certificates/client_selfsigned_cert_2048.pem
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.