node-opcua-vendor-diagnostic No license 51 versions

node-opcua-vendor-diagnostic

npm Repository Homepage

51

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation 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
dependencies	unvetted-dep:humanize	AI (dependencies): [email protected] is a long-standing pinned dependency in this established package; not a new or suspicious addition.	ai	2026/05/26
provenance	publisher-changed	AI (provenance): Transition from erossignon to GitHub Actions CI/CD with SLSA provenance; legitimate automation migration for node-opcua monorepo.	ai	2026/05/26
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; SLSA attestation confirms legitimate publish origin.	ai	2026/05/26
provenance	no-provenance	AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk signal here.	ai	2026/05/22

Versions (showing 51 of 58)

View all versions

Version	Deps	Published
2.175.2	8 / 0	2026/07/15
2.175.1	8 / 0	2026-07-13
2.175.0	8 / 0	2026-07-08
2.174.0	8 / 0	2026-06-30
2.173.1	8 / 0	2026-05-19
2.173.0	8 / 0	2026-05-19
2.172.0	8 / 0	2026-05-14
2.170.1	8 / 0	2026-05-03
2.169.0	8 / 0	2026-04-13
2.168.0	8 / 0	2026-04-04
2.167.0	8 / 0	2026-03-30
2.166.0	8 / 0	2026-03-25
2.165.2	8 / 0	2026-03-24
2.165.1	8 / 0	2026-03-20
2.165.0	8 / 0	2026-03-18
2.164.2	8 / 0	2026-03-09
2.163.1	8 / 0	2026-02-09
2.163.0	8 / 0	2026-02-07
2.162.0	8 / 0	2026-02-03
2.161.0	8 / 0	2026-01-19
2.160.0	8 / 0	2026-01-10
2.159.0	8 / 0	2025-12-16
2.158.0	8 / 0	2025-11-10
2.157.0	8 / 0	2025-09-26
2.156.0	8 / 0	2025-06-08
2.155.0	8 / 0	2025-06-06
2.154.0	8 / 0	2025-06-04
2.153.0	8 / 0	2025-05-03
2.152.0	8 / 0	2025-04-09
2.151.0	8 / 0	2025-04-06
2.150.0	8 / 0	2025-03-18
2.149.0	8 / 0	2025-02-23
2.148.0	8 / 0	2025-02-13
2.147.0	8 / 0	2025-02-13
2.146.0	8 / 0	2025-02-13
2.145.0	8 / 0	2025-02-13
2.144.0	8 / 0	2025-02-07
2.143.0	8 / 0	2025-01-30
2.142.0	8 / 0	2025-01-30
2.141.0	8 / 0	2025-01-27
2.140.0	8 / 0	2025-01-03
2.139.0	8 / 0	2024-12-15
2.138.1	8 / 0	2024-11-22
2.138.0	8 / 0	2024-11-22
2.137.0	8 / 0	2024-11-20
2.136.0	8 / 0	2024-11-11
2.135.0	8 / 0	2024-11-11
2.134.0	8 / 0	2024-11-10
2.133.0	8 / 0	2024-09-25
2.132.0	8 / 0	2024-09-13
2.131.0	8 / 0	2024-09-13

v2.175.2

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.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.175.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.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.152.0

1 finding

INFO No provenance attestation provenance

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

v2.151.0

1 finding

INFO No provenance attestation provenance

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

v2.150.0

1 finding

INFO No provenance attestation provenance

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

v2.149.0

1 finding

INFO No provenance attestation provenance

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

v2.148.0

1 finding

INFO No provenance attestation provenance

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

v2.147.0

1 finding

INFO No provenance attestation provenance

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

v2.146.0

1 finding

INFO No provenance attestation provenance

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

v2.145.0

1 finding

INFO No provenance attestation provenance

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

v2.144.0

1 finding

INFO No provenance attestation provenance

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

v2.143.0

1 finding

INFO No provenance attestation provenance

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

v2.142.0

1 finding

INFO No provenance attestation provenance

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

v2.141.0

1 finding

INFO No provenance attestation provenance

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

v2.140.0

1 finding

INFO No provenance attestation provenance

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

v2.139.0

1 finding

INFO No provenance attestation provenance

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

v2.138.1

1 finding

INFO No provenance attestation provenance

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

v2.138.0

1 finding

INFO No provenance attestation provenance

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

v2.137.0

1 finding

INFO No provenance attestation provenance

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

v2.136.0

1 finding

INFO No provenance attestation provenance

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

v2.135.0

1 finding

INFO No provenance attestation provenance

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

v2.134.0

1 finding

INFO No provenance attestation provenance

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

v2.133.0

1 finding

INFO No provenance attestation provenance

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

v2.132.0

1 finding

INFO No provenance attestation provenance

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

v2.131.0

1 finding

INFO No provenance attestation provenance

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