node-opcua-nodeid MIT 51 versions

node-opcua-nodeid

npm Repository Homepage

pure nodejs OPCUA SDK - module nodeid

51

Versions

MIT

License

No

Install Scripts

Attested

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

erossignon

Keywords

OPCUAopcuam2miotopc uainternet of things

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding is part of OPC UA NodeId byte-string parsing, not obfuscation.	ai	2026/07/23
phantom-deps	phantom-dep:node-opcua-enum	AI (phantom-deps): Monorepo sibling package likely used via re-export/type reference; stable false positive.	ai	2026/07/23
semgrep	semgrep:base64-decode	AI (semgrep): OPC-UA protocol parsing of ByteString NodeIds; base64 decode is per-spec, not obfuscation.	ai	2026/04/29

Versions (showing 51 of 101)

View all versions

Version	Deps	Published
2.175.1	3 / 2	2026-07-13
2.174.0	3 / 2	2026-06-30
2.173.0	3 / 2	2026-05-19
2.172.0	3 / 2	2026-05-14
2.169.0	3 / 2	2026-04-13
2.168.0	3 / 2	2026-04-04
2.167.0	3 / 2	2026-03-30
2.165.0	3 / 2	2026-03-18
2.164.0	3 / 2	2026-03-09
2.157.0	3 / 2	2025-09-26
2.153.0	3 / 2	2025-05-03
2.139.0	3 / 2	2024-12-15
2.133.0	3 / 2	2024-09-25
2.128.0	3 / 2	2024-07-02
2.125.0	3 / 3	2024-06-05
2.121.0	3 / 3	2024-02-25
2.120.0	3 / 3	2024-01-21
2.118.0	3 / 3	2023-11-20
2.117.0	3 / 3	2023-11-13
2.114.0	3 / 3	2023-10-02
2.113.0	3 / 3	2023-09-07
2.110.0	3 / 3	2023-08-17
2.109.0	3 / 3	2023-08-15
2.108.0	3 / 3	2023-07-18
2.105.0	3 / 3	2023-06-10
2.104.0	3 / 3	2023-06-05
2.99.0	3 / 3	2023-04-11
2.98.1	3 / 3	2023-04-10
2.98.0	3 / 3	2023-04-09
2.97.0	3 / 3	2023-04-05
2.90.1	3 / 3	2023-02-15
2.90.0	3 / 3	2023-01-29
2.88.0	3 / 3	2023-01-03
2.86.0	3 / 3	2022-12-15
2.85.0	3 / 3	2022-11-25
2.83.0	3 / 3	2022-11-14
2.82.0	6 / 3	2022-10-27
2.81.0	6 / 3	2022-10-11
2.79.0	6 / 3	2022-10-02
2.77.0	6 / 3	2022-09-08
2.76.2	6 / 3	2022-09-03
2.76.0	6 / 3	2022-09-01
2.74.0	7 / 4	2022-08-13
2.71.0	7 / 4	2022-06-25
2.70.0	7 / 4	2022-06-11
2.69.0	7 / 4	2022-06-02
2.68.0	7 / 4	2022-04-23
2.67.0	7 / 4	2022-04-18
2.66.0	7 / 4	2022-03-27
2.64.1	7 / 4	2022-02-27
2.64.0	7 / 4	2022-02-06

v2.175.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.174.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.139.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.133.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.128.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.125.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.121.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.120.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.118.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.117.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.114.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.113.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.110.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.109.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.108.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.105.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.104.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.99.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.98.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.98.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.97.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.90.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.90.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.88.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.86.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.85.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.83.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.82.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.81.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.79.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.77.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.76.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.76.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.74.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.71.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.70.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.69.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.68.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.67.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.66.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.64.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.64.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.