← Home

node-opcua-service-endpoints

npm Repository Homepage

pure nodejs OPCUA SDK - module service-endpoints

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-binary-stream AI (phantom-deps): Platform-specific/monorepo sibling dep; stable FP. ai
phantom-deps phantom-dep:node-opcua-data-model AI (phantom-deps): Monorepo sibling dep used via compiled TS output; stable FP. ai
phantom-deps phantom-dep:node-opcua-assert AI (phantom-deps): Sibling monorepo package, TS types likely used indirectly. ai
phantom-deps phantom-dep:node-opcua-nodeid AI (phantom-deps): Sibling monorepo package, TS types likely used indirectly. ai
phantom-deps phantom-dep:underscore AI (phantom-deps): Common utility likely used in compiled dist output, not source-scannable. ai
phantom-deps phantom-dep:node-opcua-factory AI (phantom-deps): Sibling monorepo package, TS types likely used indirectly. ai
phantom-deps phantom-dep:node-opcua-basic-types AI (phantom-deps): Sibling monorepo package, TS types likely used indirectly. ai
phantom-deps phantom-dep:node-opcua-service-secure-channel AI (phantom-deps): Sibling monorepo package, TS types likely used indirectly. ai
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA provenance; consistent with monorepo automation migration. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation confirms legitimate publish pipeline. ai
dependencies unvetted-dep:node-opcua-types AI (dependencies): Sibling package in the node-opcua monorepo; versioned in lockstep, stable pattern across all releases. ai

Versions (showing 51 of 180)

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

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.