← Home

node-opcua-pseudo-session

pure nodejs OPCUA SDK - module pseudo-session

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.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:node-opcua-service-filter AI (phantom-deps): Official sibling package in same monorepo, added intentionally. ai
phantom-deps phantom-dep:thenify AI (phantom-deps): Small utility likely used indirectly/transitively; stable false positive for this package. ai
phantom-deps phantom-dep:node-opcua-constants AI (phantom-deps): Sibling monorepo package, likely used via type-only or re-export import not caught by scanner. ai
phantom-deps phantom-dep:async AI (phantom-deps): Compiled TS monorepo package; dist output not scanned for imports, stable FP. ai
phantom-deps phantom-dep:node-opcua-utils AI (phantom-deps): Sibling monorepo package used via compiled dist, not source-scannable. ai
phantom-deps phantom-dep:node-opcua-status-code AI (phantom-deps): Sibling monorepo package used via compiled dist, not source-scannable. ai
phantom-deps phantom-dep:underscore AI (phantom-deps): Compiled TS monorepo package; dist output not scanned for imports, stable FP. ai
provenance publisher-changed AI (provenance): Transition from erossignon to GitHub Actions CI/CD is legitimate; SLSA attestation confirms provenance. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD migration is consistent with a monorepo tooling change, not account takeover. ai
dependencies unvetted-dep:node-opcua-service-write AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-service-browse AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-types AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
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
dependencies unvetted-dep:node-opcua-service-subscription AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-nodeid AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-variant AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-data-model AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-data-value AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-basic-types AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-status-code AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-service-call AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai
dependencies unvetted-dep:node-opcua-service-read AI (dependencies): Sibling monorepo package from node-opcua; same versioning cadence, not an independent risk. ai

Versions (showing 51 of 204)

View all versions
Version Deps Published
2.175.2 17 / 0
2.175.1 17 / 0
2.174.0 17 / 0
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 19 / 0
2.155.0 19 / 0
2.154.0 19 / 0
2.153.0 19 / 0
2.152.0 19 / 0
2.151.0 19 / 0
2.150.0 19 / 0
2.149.0 19 / 0
2.143.0 19 / 0
2.142.0 19 / 0
2.141.0 19 / 0
2.140.0 19 / 0
2.139.0 19 / 0
2.138.0 19 / 0
2.137.0 19 / 0
2.134.0 19 / 0
2.133.0 19 / 0
2.132.0 19 / 0
2.131.0 19 / 0
2.130.0 19 / 0
2.129.0 19 / 0
2.128.0 19 / 0
2.127.1 19 / 0
2.127.0 19 / 0
2.126.0 19 / 0
2.125.0 19 / 0
2.124.0 19 / 0
2.123.0 19 / 0
2.121.0 19 / 0

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.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
LOW No provenance attestation provenance

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

v2.151.0

1 finding
LOW No provenance attestation provenance

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

v2.150.0

1 finding
LOW No provenance attestation provenance

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

v2.149.0

1 finding
LOW No provenance attestation provenance

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

v2.143.0

1 finding
LOW No provenance attestation provenance

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

v2.142.0

1 finding
LOW No provenance attestation provenance

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

v2.141.0

1 finding
LOW No provenance attestation provenance

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

v2.140.0

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v2.137.0

1 finding
LOW No provenance attestation provenance

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

v2.134.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.132.0

1 finding
LOW No provenance attestation provenance

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

v2.131.0

1 finding
LOW No provenance attestation provenance

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

v2.130.0

1 finding
LOW No provenance attestation provenance

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

v2.129.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.127.1

1 finding
LOW No provenance attestation provenance

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

v2.127.0

1 finding
LOW No provenance attestation provenance

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

v2.126.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.124.0

1 finding
LOW No provenance attestation provenance

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

v2.123.0

1 finding
LOW No provenance attestation provenance

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

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.