node-opcua-service-read
pure nodejs OPCUA SDK - module service-read
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-opcua-nodeid | AI (phantom-deps): Sibling monorepo package, likely type-only/re-export usage. | ai | |
| phantom-deps | phantom-dep:underscore | AI (phantom-deps): Common utility dep in this monorepo, false positive pattern. | ai | |
| phantom-deps | phantom-dep:node-opcua-basic-types | AI (phantom-deps): Sibling monorepo package, likely type-only/re-export usage. | ai | |
| phantom-deps | phantom-dep:node-opcua-factory | AI (phantom-deps): Sibling monorepo package, likely type-only/re-export usage. | ai | |
| phantom-deps | phantom-dep:node-opcua-numeric-range | AI (phantom-deps): Sibling monorepo package, likely type-only/re-export usage. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects CI/CD migration, not account takeover; SLSA provenance confirms legitimate automated publishing. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from erossignon to GitHub Actions CI/CD is documented by SLSA attestation; stable for this package going forward. | ai | |
| dependencies | unvetted-dep:node-opcua-types | AI (dependencies): Sibling monorepo package at matching version; stable pattern across all node-opcua releases. | ai | |
| dependencies | unvetted-dep:node-opcua-service-secure-channel | AI (dependencies): Sibling monorepo package at matching version; stable pattern across all node-opcua releases. | ai | |
| dependencies | unvetted-dep:node-opcua-data-value | AI (dependencies): Sibling monorepo package at matching version; stable pattern across all node-opcua releases. | ai | |
| dependencies | unvetted-dep:node-opcua-data-model | AI (dependencies): Sibling monorepo package at matching version; stable pattern across all node-opcua releases. | ai |
Versions (showing 80 of 180)
| Version | Deps | Published |
|---|---|---|
| 2.63.2 | 10 / 2 | |
| 2.63.1 | 10 / 2 | |
| 2.63.0 | 10 / 2 | |
| 2.62.7 | 10 / 2 | |
| 2.62.6 | 10 / 2 | |
| 2.62.5 | 10 / 2 | |
| 2.62.4 | 10 / 2 | |
| 2.62.0 | 10 / 2 | |
| 2.61.0 | 10 / 2 | |
| 2.60.0 | 10 / 2 | |
| 2.59.0 | 10 / 2 | |
| 2.57.0 | 10 / 2 | |
| 2.56.2 | 10 / 2 | |
| 2.56.0 | 10 / 2 | |
| 2.55.0 | 10 / 2 | |
| 2.54.0 | 10 / 2 | |
| 2.53.0 | 10 / 2 | |
| 2.52.0 | 10 / 2 | |
| 2.51.0 | 10 / 2 | |
| 2.49.0 | 10 / 2 | |
| 2.48.0 | 10 / 2 | |
| 2.47.0 | 10 / 2 | |
| 2.45.0 | 10 / 2 | |
| 2.44.0 | 10 / 2 | |
| 2.42.0 | 10 / 2 | |
| 2.41.1 | 10 / 2 | |
| 2.41.0 | 10 / 2 | |
| 2.40.0 | 10 / 2 | |
| 2.37.0 | 10 / 2 | |
| 2.36.0 | 10 / 2 | |
| 2.35.0 | 10 / 2 | |
| 2.34.0 | 10 / 3 | |
| 2.32.0 | 10 / 3 | |
| 2.31.0 | 10 / 3 | |
| 2.29.0 | 10 / 3 | |
| 2.28.1 | 10 / 3 | |
| 2.28.0 | 10 / 3 | |
| 2.27.1 | 10 / 3 | |
| 2.27.0 | 10 / 3 | |
| 2.26.0 | 10 / 3 | |
| 2.25.0 | 10 / 3 | |
| 2.24.0 | 10 / 3 | |
| 2.22.0 | 10 / 3 | |
| 2.21.0 | 10 / 3 | |
| 2.20.0 | 10 / 3 | |
| 2.19.0 | 10 / 3 | |
| 2.17.0 | 10 / 3 | |
| 2.16.0 | 10 / 3 | |
| 2.15.0 | 11 / 3 | |
| 2.13.0 | 11 / 3 | |
| 2.11.0 | 11 / 3 | |
| 2.10.0 | 11 / 3 | |
| 2.9.0 | 11 / 3 | |
| 2.8.1 | 11 / 3 | |
| 2.8.0 | 11 / 3 | |
| 2.7.0 | 11 / 3 | |
| 2.6.5 | 11 / 3 | |
| 2.6.4 | 11 / 3 | |
| 2.6.1 | 11 / 3 | |
| 2.5.10 | 11 / 3 | |
| 2.5.9 | 11 / 3 | |
| 2.5.8 | 11 / 3 | |
| 2.5.7 | 11 / 3 | |
| 2.5.6 | 11 / 3 | |
| 2.5.5 | 11 / 3 | |
| 2.5.4 | 11 / 3 | |
| 2.5.2 | 11 / 3 | |
| 2.5.1 | 11 / 3 | |
| 2.4.2 | 11 / 3 | |
| 2.4.0 | 11 / 3 | |
| 2.3.0 | 11 / 3 | |
| 2.2.0 | 11 / 3 | |
| 2.1.8 | 11 / 3 | |
| 2.1.6 | 11 / 3 | |
| 2.1.5 | 11 / 3 | |
| 2.1.3 | 11 / 3 | |
| 2.1.2 | 11 / 3 | |
| 2.1.1 | 11 / 3 | |
| 2.1.0 | 11 / 3 | |
| 2.0.0 | 11 / 3 |
v2.63.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.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.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.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.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.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.