← Home

node-opcua-client-dynamic-extension-object

npm Repository Homepage

pure nodejs OPCUA SDK - module client-dynamic-extension-object

23
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 personal account to GitHub Actions CI/CD with SLSA attestation; legitimate automation upgrade for node-opcua monorepo. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; package is actively maintained with 234 versions and 66k weekly downloads. ai
dependencies unvetted-dep:node-opcua-factory AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-schemas AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-variant AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-data-model AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-data-value AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-types AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-binary-stream AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-pseudo-session AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-service-browse AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-extension-object AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-service-translate-browse-path AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-status-code AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai
dependencies unvetted-dep:node-opcua-nodeid AI (dependencies): Sibling package in the node-opcua monorepo; same publisher, same versioning cadence. ai

Versions (showing 23 of 23)

Version Deps Published
2.173.0 17 / 0
2.172.0 17 / 0
2.170.1 17 / 0
2.169.0 17 / 0
2.168.0 17 / 0
2.167.0 17 / 0
2.166.0 17 / 0
2.165.2 17 / 0
2.165.1 17 / 0
2.165.0 17 / 0
2.164.2 17 / 0
2.163.1 17 / 0
2.163.0 17 / 0
2.162.0 17 / 0
2.161.0 17 / 0
2.160.0 17 / 0
2.159.0 17 / 0
2.158.0 17 / 0
2.157.0 17 / 0
2.156.0 17 / 0
2.155.0 17 / 0
2.154.0 17 / 0
2.153.0 17 / 0

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.156.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.