node-opcua-status-code
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-assert | AI (dependencies): Same node-opcua monorepo family; stable sibling dependency pattern across all versions. | ai | |
| dependencies | unvetted-dep:node-opcua-binary-stream | AI (dependencies): Same node-opcua monorepo family; stable sibling dependency pattern across all versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.173.0 | 2 / 0 | |
| 2.172.0 | 2 / 0 | |
| 2.169.0 | 2 / 0 | |
| 2.168.0 | 2 / 0 | |
| 2.167.0 | 2 / 0 | |
| 2.165.0 | 2 / 0 | |
| 2.164.0 | 2 / 0 | |
| 2.162.0 | 2 / 0 | |
| 2.157.0 | 2 / 0 | |
| 2.153.0 | 2 / 0 |
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.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.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.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.157.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.