node-opcua-client-dynamic-extension-object
pure nodejs OPCUA SDK - module client-dynamic-extension-object
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 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 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 2.76.0 | 16 / 0 | |
| 2.43.0 | 16 / 0 | |
| 2.42.0 | 16 / 0 | |
| 2.41.1 | 16 / 0 | |
| 2.41.0 | 16 / 0 | |
| 2.40.0 | 16 / 0 | |
| 2.37.0 | 16 / 0 | |
| 2.36.0 | 16 / 0 | |
| 2.35.0 | 16 / 0 | |
| 2.34.0 | 16 / 0 | |
| 2.32.0 | 16 / 0 | |
| 2.31.0 | 16 / 0 | |
| 2.29.0 | 16 / 0 | |
| 2.28.1 | 16 / 0 | |
| 2.28.0 | 16 / 0 | |
| 2.27.1 | 16 / 0 | |
| 2.27.0 | 16 / 0 | |
| 2.26.0 | 16 / 0 | |
| 2.25.0 | 16 / 0 | |
| 2.24.0 | 16 / 0 | |
| 2.22.0 | 16 / 0 | |
| 2.21.0 | 16 / 0 | |
| 2.20.0 | 16 / 0 | |
| 2.19.0 | 16 / 0 | |
| 2.17.0 | 16 / 0 | |
| 2.16.0 | 16 / 0 | |
| 2.15.0 | 16 / 0 | |
| 2.13.0 | 16 / 0 | |
| 2.12.0 | 16 / 0 | |
| 2.11.0 | 16 / 0 | |
| 2.10.0 | 16 / 0 | |
| 2.9.0 | 16 / 0 | |
| 2.8.1 | 16 / 0 | |
| 2.8.0 | 16 / 0 | |
| 2.7.0 | 16 / 0 | |
| 2.6.7 | 16 / 0 | |
| 2.6.5 | 16 / 0 | |
| 2.6.4 | 16 / 0 | |
| 2.6.2 | 16 / 0 | |
| 2.6.1 | 16 / 0 | |
| 2.5.10 | 16 / 0 | |
| 2.5.9 | 16 / 0 | |
| 2.5.8 | 16 / 0 | |
| 2.5.7 | 16 / 0 | |
| 2.5.6 | 16 / 0 | |
| 2.5.5 | 16 / 0 | |
| 2.5.4 | 16 / 0 | |
| 2.5.2 | 16 / 0 | |
| 2.5.1 | 16 / 0 |
v2.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.