← Home

node-opcua-secure-channel

npm Repository Homepage

pure nodejs OPCUA SDK - module secure-channel

22
Versions
MIT
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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from erossignon to GitHub Actions CI/CD publishing; SLSA attestation confirms legitimate automated pipeline. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA provenance attestation confirms legitimate publish from the official repo. ai
dependencies unvetted-dep:node-opcua-common AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-nodeid AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-factory AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-transport AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-basic-types AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-status-code AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-types AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-binary-stream AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-packet-analyzer AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-service-endpoints AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-certificate-manager AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-service-secure-channel AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-chunkmanager AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai
dependencies unvetted-dep:node-opcua-utils AI (dependencies): Sibling monorepo package; same publisher, same version cadence. ai

Versions (showing 22 of 22)

Version Deps Published
2.173.0 19 / 7
2.172.0 19 / 7
2.170.1 20 / 7
2.169.0 20 / 7
2.168.0 20 / 7
2.167.0 21 / 7
2.166.0 21 / 7
2.165.2 21 / 7
2.165.1 21 / 7
2.165.0 21 / 7
2.164.2 21 / 7
2.163.1 21 / 7
2.163.0 21 / 7
2.162.0 21 / 7
2.161.0 21 / 7
2.160.0 21 / 7
2.159.0 21 / 7
2.158.0 21 / 7
2.157.0 21 / 7
2.155.0 20 / 7
2.154.0 20 / 7
2.153.0 20 / 7

v2.173.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.172.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.170.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.169.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.166.0

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-03-25) provenance

This version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.

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.165.2

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-03-24) provenance

This version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.

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.165.1

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-03-20) provenance

This version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.

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.165.0

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-03-18) provenance

This version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.

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.164.2

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-03-09) provenance

This version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.

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.163.1

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-02-09) provenance

This version was published by a different npm account than previous versions on 2026-02-09. This could indicate a legitimate maintainer transition or an account compromise.

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.163.0

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-02-07) provenance

This version was published by a different npm account than previous versions on 2026-02-07. This could indicate a legitimate maintainer transition or an account compromise.

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.162.0

2 findings
HIGH Publisher changed: erossignon → GitHub Actions (on 2026-02-03) provenance

This version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.

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.161.0

1 finding
LOW No provenance attestation provenance

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

v2.160.0

1 finding
LOW No provenance attestation provenance

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

v2.159.0

1 finding
LOW No provenance attestation provenance

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

v2.158.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.157.0

1 finding
LOW No provenance attestation provenance

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

v2.155.0

1 finding
LOW No provenance attestation provenance

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

v2.154.0

1 finding
LOW No provenance attestation provenance

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

v2.153.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.