node-opcua-data-value
pure nodejs OPCUA SDK - module data-value
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-utils | AI (phantom-deps): Sibling monorepo package, likely used indirectly via TS compilation. | ai | |
| phantom-deps | phantom-dep:node-opcua-nodeid | AI (phantom-deps): Sibling monorepo package, likely used indirectly via TS compilation. | ai | |
| phantom-deps | phantom-dep:node-opcua-extension-object | AI (phantom-deps): Sibling monorepo package, likely used indirectly via TS compilation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from erossignon to GitHub Actions CI/CD is legitimate; SLSA attestation confirms automated publishing pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo publishing cadence, not account takeover; SLSA provenance and repo continuity confirm legitimacy. | ai | |
| dependencies | unvetted-dep:node-opcua-data-model | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-basic-types | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-enum | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-binary-stream | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-status-code | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-debug | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-factory | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-variant | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-date-time | AI (dependencies): Sibling package in node-opcua monorepo; same publisher, same release cadence. | ai |
Versions (showing 51 of 163)
| Version | Deps | Published |
|---|---|---|
| 2.175.1 | 10 / 3 | |
| 2.174.0 | 10 / 3 | |
| 2.173.0 | 10 / 3 | |
| 2.172.0 | 10 / 3 | |
| 2.170.0 | 10 / 3 | |
| 2.169.0 | 10 / 3 | |
| 2.168.0 | 10 / 3 | |
| 2.167.0 | 10 / 3 | |
| 2.165.0 | 10 / 3 | |
| 2.164.0 | 10 / 3 | |
| 2.163.0 | 10 / 3 | |
| 2.162.0 | 10 / 3 | |
| 2.161.0 | 10 / 3 | |
| 2.159.0 | 10 / 3 | |
| 2.158.0 | 10 / 3 | |
| 2.157.0 | 10 / 3 | |
| 2.155.0 | 9 / 4 | |
| 2.154.0 | 9 / 4 | |
| 2.153.0 | 9 / 4 | |
| 2.151.0 | 9 / 4 | |
| 2.150.0 | 9 / 4 | |
| 2.142.0 | 9 / 4 | |
| 2.139.0 | 9 / 4 | |
| 2.137.0 | 9 / 4 | |
| 2.134.0 | 9 / 4 | |
| 2.133.0 | 9 / 4 | |
| 2.132.0 | 9 / 4 | |
| 2.131.0 | 9 / 4 | |
| 2.129.0 | 9 / 4 | |
| 2.128.0 | 9 / 4 | |
| 2.126.0 | 9 / 5 | |
| 2.125.0 | 9 / 5 | |
| 2.121.0 | 9 / 5 | |
| 2.120.0 | 9 / 5 | |
| 2.119.0 | 9 / 5 | |
| 2.118.0 | 9 / 5 | |
| 2.117.0 | 9 / 5 | |
| 2.114.0 | 9 / 5 | |
| 2.113.0 | 9 / 5 | |
| 2.112.0 | 9 / 5 | |
| 2.111.0 | 9 / 5 | |
| 2.110.0 | 9 / 5 | |
| 2.109.0 | 9 / 5 | |
| 2.108.0 | 9 / 5 | |
| 2.105.0 | 9 / 5 | |
| 2.104.0 | 9 / 5 | |
| 2.102.0 | 9 / 5 | |
| 2.99.0 | 9 / 5 | |
| 2.98.1 | 9 / 5 | |
| 2.98.0 | 9 / 5 | |
| 2.97.0 | 9 / 5 |
v2.175.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.174.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.151.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.150.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.142.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.139.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.134.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.133.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.132.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.131.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.129.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.128.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.126.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.125.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.121.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.120.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.113.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.112.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.110.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.109.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.