← Home

node-opcua-service-session

pure nodejs OPCUA SDK - module service-session

51
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
phantom-deps phantom-dep:node-opcua-binary-stream AI (phantom-deps): Platform-specific binary dep, expected false positive. ai
phantom-deps phantom-dep:node-opcua-basic-types AI (phantom-deps): Sibling node-opcua package, real usage obscured by build. ai
phantom-deps phantom-dep:node-opcua-extension-object AI (phantom-deps): Sibling node-opcua package, real usage obscured by build. ai
phantom-deps phantom-dep:node-opcua-service-endpoints AI (phantom-deps): Sibling node-opcua package, real usage obscured by build. ai
phantom-deps phantom-dep:node-opcua-service-secure-channel AI (phantom-deps): Sibling node-opcua package, real usage obscured by build. ai
phantom-deps phantom-dep:underscore AI (phantom-deps): Monorepo submodule; used dep flagged by heuristic due to TS compilation. ai
phantom-deps phantom-dep:node-opcua-assert AI (phantom-deps): Sibling node-opcua package, real usage obscured by build. ai
phantom-deps phantom-dep:node-opcua-nodeid AI (phantom-deps): Sibling node-opcua package, real usage obscured by build. ai
provenance publisher-changed AI (provenance): Transition from erossignon to GitHub Actions CI/CD publishing; confirmed by SLSA provenance attestation on this and likely future versions. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; SLSA attestation confirms legitimate automated publishing. ai
dependencies unvetted-dep:node-opcua-factory AI (dependencies): Sibling monorepo package from the same node-opcua project, versioned in lockstep. ai
dependencies unvetted-dep:node-opcua-types AI (dependencies): Sibling monorepo package from the same node-opcua project, versioned in lockstep. ai

Versions (showing 51 of 180)

View all versions
Version Deps Published
2.175.2 2 / 1
2.175.1 2 / 1
2.174.0 2 / 1
2.173.0 2 / 1
2.172.0 2 / 1
2.170.0 2 / 1
2.169.0 2 / 1
2.168.0 2 / 1
2.167.0 2 / 1
2.165.0 2 / 1
2.164.0 2 / 1
2.163.1 2 / 1
2.163.0 2 / 1
2.162.0 2 / 1
2.161.0 2 / 1
2.159.0 2 / 1
2.158.0 2 / 1
2.157.0 2 / 1
2.155.0 2 / 1
2.154.0 2 / 1
2.153.0 2 / 1
2.151.0 2 / 1
2.150.0 2 / 1
2.143.0 2 / 1
2.142.0 2 / 1
2.141.0 2 / 1
2.139.0 2 / 1
2.137.0 2 / 1
2.134.0 2 / 1
2.133.0 2 / 1
2.132.0 2 / 1
2.131.0 2 / 1
2.129.0 2 / 1
2.128.0 2 / 1
2.126.0 2 / 2
2.125.0 2 / 2
2.123.0 2 / 2
2.121.0 2 / 2
2.120.0 2 / 2
2.119.2 2 / 2
2.119.0 2 / 2
2.118.0 2 / 2
2.117.0 2 / 2
2.114.0 2 / 2
2.113.0 2 / 2
2.112.0 2 / 2
2.111.0 2 / 2
2.110.0 2 / 2
2.109.0 2 / 2
2.108.0 2 / 2
2.107.0 2 / 2

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

v2.120.0

1 finding
LOW No provenance attestation provenance

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

v2.119.2

1 finding
LOW No provenance attestation provenance

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

v2.119.0

1 finding
LOW No provenance attestation provenance

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

v2.118.0

1 finding
LOW No provenance attestation provenance

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

v2.117.0

1 finding
LOW No provenance attestation provenance

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

v2.114.0

1 finding
LOW No provenance attestation provenance

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

v2.113.0

1 finding
LOW No provenance attestation provenance

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

v2.112.0

1 finding
LOW No provenance attestation provenance

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

v2.111.0

1 finding
LOW No provenance attestation provenance

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

v2.110.0

1 finding
LOW No provenance attestation provenance

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

v2.109.0

1 finding
LOW No provenance attestation provenance

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

v2.108.0

1 finding
LOW No provenance attestation provenance

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

v2.107.0

1 finding
LOW No provenance attestation provenance

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