node-opcua-address-space-base
pure nodejs OPCUA SDK - module address-space-base
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:async | AI (phantom-deps): Monorepo TS build; likely used transitively/in dist output. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Same pattern; benign utility dep. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Same pattern; benign utility dep. | ai | |
| phantom-deps | phantom-dep:dequeue | AI (phantom-deps): Same pattern; benign utility dep. | ai | |
| phantom-deps | phantom-dep:thenify | AI (phantom-deps): Same pattern; benign utility dep. | ai | |
| phantom-deps | phantom-dep:xml-writer | AI (phantom-deps): Same pattern; benign utility dep. | ai | |
| phantom-deps | phantom-dep:pretty-error | AI (phantom-deps): Same pattern; benign utility dep. | ai | |
| phantom-deps | phantom-dep:node-opcua-debug | AI (phantom-deps): Sibling monorepo package, used indirectly. | ai | |
| phantom-deps | phantom-dep:set-prototype-of | AI (phantom-deps): Same pattern; benign utility dep. | ai | |
| phantom-deps | phantom-dep:node-opcua-assert | AI (phantom-deps): Sibling monorepo package. | ai | |
| phantom-deps | phantom-dep:node-opcua-xml2json | AI (phantom-deps): Sibling monorepo package. | ai | |
| dependencies | unvetted-dep:node-opcua-status-code | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-debug | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-extension-object | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-numeric-range | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-types | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-crypto | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-nodeid | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-schemas | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-variant | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-constants | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-date-time | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-data-model | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-data-value | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai | |
| dependencies | unvetted-dep:node-opcua-basic-types | AI (dependencies): Sibling package from same node-opcua monorepo; no independent threat. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 2.175.2 | 15 / 0 | |
| 2.175.1 | 15 / 0 | |
| 2.174.0 | 15 / 0 | |
| 2.173.0 | 15 / 0 | |
| 2.172.0 | 15 / 0 | |
| 2.170.1 | 15 / 0 | |
| 2.169.0 | 15 / 0 | |
| 2.168.0 | 15 / 0 | |
| 2.167.0 | 15 / 0 | |
| 2.165.0 | 15 / 0 | |
| 2.164.0 | 15 / 0 | |
| 2.163.1 | 15 / 0 | |
| 2.163.0 | 15 / 0 | |
| 2.162.0 | 15 / 0 | |
| 2.161.0 | 15 / 0 | |
| 2.159.0 | 15 / 0 | |
| 2.158.0 | 15 / 0 | |
| 2.157.0 | 15 / 0 | |
| 2.155.0 | 15 / 0 | |
| 2.154.0 | 15 / 0 | |
| 2.153.0 | 15 / 0 | |
| 2.151.0 | 15 / 0 | |
| 2.150.0 | 15 / 0 | |
| 2.149.0 | 15 / 0 | |
| 2.143.0 | 15 / 0 | |
| 2.142.0 | 15 / 0 | |
| 2.141.0 | 15 / 0 | |
| 2.139.0 | 15 / 0 | |
| 2.138.0 | 15 / 0 | |
| 2.137.0 | 15 / 0 | |
| 2.134.0 | 15 / 0 | |
| 2.133.0 | 15 / 0 | |
| 2.132.0 | 15 / 0 | |
| 2.131.0 | 15 / 0 | |
| 2.129.0 | 15 / 0 | |
| 2.128.0 | 15 / 0 | |
| 2.126.0 | 15 / 0 | |
| 2.125.0 | 15 / 0 | |
| 2.123.0 | 15 / 0 | |
| 2.121.0 | 15 / 0 | |
| 2.120.0 | 15 / 0 | |
| 2.119.2 | 15 / 0 | |
| 2.119.0 | 15 / 0 | |
| 2.118.0 | 15 / 0 | |
| 2.117.0 | 15 / 0 | |
| 2.114.0 | 15 / 0 | |
| 2.113.0 | 15 / 0 | |
| 2.112.0 | 15 / 0 | |
| 2.111.0 | 15 / 0 | |
| 2.110.0 | 15 / 0 | |
| 2.109.0 | 15 / 0 |
v2.175.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.149.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.143.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.141.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.138.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.123.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
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.