node-opcua
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-opcua-aggregates | AI (dependencies): First-party monorepo sub-package; same publisher and version cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-client-proxy | AI (dependencies): First-party monorepo sub-package; same publisher and version cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-server-discovery | AI (dependencies): First-party monorepo sub-package; same publisher and version cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-vendor-diagnostic | AI (dependencies): First-party monorepo sub-package; same publisher and version cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-address-space-for-conformance-testing | AI (dependencies): First-party monorepo sub-package; same publisher and version cadence. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): Type-only package; loaded by convention in TypeScript projects. | ai | |
| phantom-deps | phantom-dep:node-opcua-enum | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-types | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-crypto | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-factory | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-client-proxy | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-secure-channel | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-packet-analyzer | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-vendor-diagnostic | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-opcua-address-space-for-conformance-testing | AI (phantom-deps): Monorepo config-referenced sub-package; stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.173.1 | 50 / 0 | |
| 2.173.0 | 50 / 0 | |
| 2.172.0 | 50 / 0 | |
| 2.170.1 | 50 / 0 | |
| 2.169.0 | 50 / 0 | |
| 2.168.0 | 50 / 0 | |
| 2.167.0 | 50 / 0 | |
| 2.166.0 | 50 / 0 | |
| 2.165.2 | 50 / 0 | |
| 2.165.1 | 50 / 0 | |
| 2.165.0 | 50 / 0 | |
| 2.164.2 | 50 / 0 | |
| 2.163.1 | 50 / 0 | |
| 2.163.0 | 50 / 0 | |
| 2.162.0 | 50 / 0 | |
| 2.161.0 | 50 / 0 | |
| 2.160.0 | 50 / 0 | |
| 2.159.0 | 50 / 0 | |
| 2.158.0 | 50 / 0 | |
| 2.157.0 | 50 / 0 | |
| 2.156.0 | 50 / 0 | |
| 2.155.0 | 50 / 0 | |
| 2.154.0 | 50 / 0 | |
| 2.153.0 | 50 / 0 |
v2.173.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.173.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.172.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.170.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.169.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.168.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.167.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.166.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.165.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.165.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.165.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.164.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.163.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.163.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.162.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.161.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.160.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.159.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.158.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.157.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.156.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.155.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.154.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.153.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.