node-opcua-pseudo-session MIT 23 versions

node-opcua-pseudo-session

npm Repository Homepage

pure nodejs OPCUA SDK - module pseudo-session

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.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition from erossignon to GitHub Actions CI/CD is legitimate; SLSA attestation confirms provenance.	ai	2026/05/19
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by CI/CD migration is consistent with a monorepo tooling change, not account takeover.	ai	2026/05/19
dependencies	unvetted-dep:node-opcua-variant	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-data-model	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-data-value	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-basic-types	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-status-code	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-types	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-service-read	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-service-write	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-service-browse	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-service-subscription	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-service-translate-browse-path	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-service-call	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-nodeid	AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk.	ai	2026/04/29

Versions (showing 23 of 23)

Version	Deps	Published
2.173.0	17 / 0	2026-05-19
2.172.0	17 / 0	2026-05-14
2.170.1	17 / 0	2026-05-03
2.169.0	17 / 0	2026-04-13
2.168.0	17 / 0	2026-04-04
2.167.0	17 / 0	2026-03-30
2.166.0	17 / 0	2026-03-25
2.165.2	17 / 0	2026-03-24
2.165.1	17 / 0	2026-03-20
2.165.0	17 / 0	2026-03-18
2.164.2	17 / 0	2026-03-09
2.163.1	17 / 0	2026-02-09
2.163.0	17 / 0	2026-02-07
2.162.0	17 / 0	2026-02-03
2.161.0	17 / 0	2026-01-19
2.160.0	17 / 0	2026-01-10
2.159.0	17 / 0	2025-12-16
2.158.0	17 / 0	2025-11-10
2.157.0	17 / 0	2025-09-26
2.156.0	19 / 0	2025-06-08
2.155.0	19 / 0	2025-06-06
2.154.0	19 / 0	2025-06-04
2.153.0	19 / 0	2025-05-03

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