node-opcua-xml2json
pure nodejs OPCUA SDK - module xml2json
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard base64 decode for OPC-UA extension object parsing, not payload obfuscation. | ai | |
| phantom-deps | phantom-dep:node-opcua-debug | AI (phantom-deps): Sibling monorepo package, likely used indirectly; stable false positive. | ai |
Versions (showing 100 of 128)
| Version | Deps | Published |
|---|---|---|
| 2.175.2 | 3 / 1 | |
| 2.175.1 | 3 / 1 | |
| 2.173.0 | 3 / 1 | |
| 2.172.0 | 3 / 1 | |
| 2.169.0 | 3 / 1 | |
| 2.168.0 | 3 / 1 | |
| 2.167.0 | 3 / 1 | |
| 2.165.0 | 3 / 1 | |
| 2.164.0 | 3 / 1 | |
| 2.163.1 | 3 / 1 | |
| 2.163.0 | 3 / 2 | |
| 2.162.0 | 3 / 2 | |
| 2.157.0 | 3 / 2 | |
| 2.155.0 | 3 / 2 | |
| 2.154.0 | 3 / 2 | |
| 2.153.0 | 3 / 2 | |
| 2.143.0 | 3 / 2 | |
| 2.142.0 | 5 / 2 | |
| 2.141.0 | 5 / 2 | |
| 2.139.0 | 5 / 2 | |
| 2.137.0 | 5 / 2 | |
| 2.133.0 | 5 / 2 | |
| 2.128.0 | 5 / 2 | |
| 2.125.0 | 5 / 4 | |
| 2.123.0 | 5 / 4 | |
| 2.121.0 | 5 / 4 | |
| 2.120.0 | 5 / 4 | |
| 2.119.2 | 5 / 4 | |
| 2.118.0 | 5 / 4 | |
| 2.117.0 | 5 / 4 | |
| 2.114.0 | 5 / 4 | |
| 2.113.0 | 5 / 4 | |
| 2.110.0 | 5 / 4 | |
| 2.109.0 | 5 / 4 | |
| 2.108.0 | 5 / 4 | |
| 2.107.0 | 5 / 4 | |
| 2.105.0 | 5 / 4 | |
| 2.104.0 | 5 / 4 | |
| 2.103.0 | 5 / 4 | |
| 2.99.0 | 5 / 4 | |
| 2.98.2 | 5 / 4 | |
| 2.98.1 | 5 / 4 | |
| 2.98.0 | 5 / 4 | |
| 2.96.0 | 5 / 4 | |
| 2.90.1 | 5 / 4 | |
| 2.90.0 | 5 / 4 | |
| 2.88.0 | 5 / 4 | |
| 2.86.0 | 5 / 4 | |
| 2.85.0 | 5 / 4 | |
| 2.83.0 | 5 / 4 | |
| 2.82.0 | 5 / 4 | |
| 2.77.0 | 5 / 4 | |
| 2.76.2 | 5 / 4 | |
| 2.76.0 | 5 / 4 | |
| 2.74.0 | 6 / 2 | |
| 2.73.0 | 6 / 2 | |
| 2.71.0 | 6 / 2 | |
| 2.70.3 | 6 / 2 | |
| 2.70.2 | 6 / 2 | |
| 2.70.0 | 6 / 2 | |
| 2.69.0 | 6 / 2 | |
| 2.68.0 | 6 / 2 | |
| 2.67.0 | 6 / 2 | |
| 2.66.0 | 6 / 2 | |
| 2.64.1 | 6 / 2 | |
| 2.64.0 | 6 / 2 | |
| 2.63.2 | 6 / 2 | |
| 2.63.1 | 6 / 2 | |
| 2.63.0 | 6 / 2 | |
| 2.62.7 | 6 / 2 | |
| 2.62.6 | 6 / 2 | |
| 2.62.5 | 6 / 2 | |
| 2.62.4 | 6 / 2 | |
| 2.61.0 | 6 / 2 | |
| 2.60.0 | 6 / 2 | |
| 2.57.0 | 6 / 2 | |
| 2.56.0 | 6 / 2 | |
| 2.55.0 | 6 / 2 | |
| 2.54.0 | 6 / 2 | |
| 2.52.0 | 6 / 2 | |
| 2.51.0 | 6 / 2 | |
| 2.49.0 | 6 / 2 | |
| 2.44.0 | 6 / 2 | |
| 2.42.0 | 6 / 2 | |
| 2.41.1 | 6 / 2 | |
| 2.41.0 | 6 / 2 | |
| 2.40.0 | 6 / 2 | |
| 2.37.0 | 6 / 2 | |
| 2.36.0 | 6 / 2 | |
| 2.35.0 | 6 / 2 | |
| 2.34.0 | 6 / 2 | |
| 2.32.0 | 6 / 2 | |
| 2.31.0 | 6 / 2 | |
| 2.29.0 | 6 / 2 | |
| 2.28.0 | 6 / 2 | |
| 2.27.1 | 6 / 2 | |
| 2.27.0 | 6 / 2 | |
| 2.26.0 | 6 / 2 | |
| 2.25.0 | 6 / 2 | |
| 2.22.0 | 6 / 2 |
v2.175.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.175.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.143.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.142.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.141.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.139.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.137.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.133.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.128.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.125.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.123.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.120.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.119.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.118.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.117.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.114.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.113.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.110.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.109.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.108.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.105.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.103.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.88.0
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.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.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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.71.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.0
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.0
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.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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.5
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.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.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.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.54.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.51.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.44.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.1
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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.