node-opcua-vendor-diagnostic
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:humanize | AI (dependencies): [email protected] is a long-standing pinned dependency in this established package; not a new or suspicious addition. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from erossignon to GitHub Actions CI/CD with SLSA provenance; legitimate automation migration for node-opcua monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; SLSA attestation confirms legitimate publish origin. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 2.175.2 | 8 / 0 | |
| 2.175.1 | 8 / 0 | |
| 2.175.0 | 8 / 0 | |
| 2.174.0 | 8 / 0 | |
| 2.173.1 | 8 / 0 | |
| 2.173.0 | 8 / 0 | |
| 2.172.0 | 8 / 0 | |
| 2.170.1 | 8 / 0 | |
| 2.169.0 | 8 / 0 | |
| 2.168.0 | 8 / 0 | |
| 2.167.0 | 8 / 0 | |
| 2.166.0 | 8 / 0 | |
| 2.165.2 | 8 / 0 | |
| 2.165.1 | 8 / 0 | |
| 2.165.0 | 8 / 0 | |
| 2.164.2 | 8 / 0 | |
| 2.163.1 | 8 / 0 | |
| 2.163.0 | 8 / 0 | |
| 2.162.0 | 8 / 0 | |
| 2.161.0 | 8 / 0 | |
| 2.160.0 | 8 / 0 | |
| 2.159.0 | 8 / 0 | |
| 2.158.0 | 8 / 0 | |
| 2.157.0 | 8 / 0 | |
| 2.156.0 | 8 / 0 | |
| 2.155.0 | 8 / 0 | |
| 2.154.0 | 8 / 0 | |
| 2.153.0 | 8 / 0 | |
| 2.152.0 | 8 / 0 | |
| 2.151.0 | 8 / 0 | |
| 2.150.0 | 8 / 0 | |
| 2.149.0 | 8 / 0 | |
| 2.148.0 | 8 / 0 | |
| 2.147.0 | 8 / 0 | |
| 2.146.0 | 8 / 0 | |
| 2.145.0 | 8 / 0 | |
| 2.144.0 | 8 / 0 | |
| 2.143.0 | 8 / 0 | |
| 2.142.0 | 8 / 0 | |
| 2.141.0 | 8 / 0 | |
| 2.140.0 | 8 / 0 | |
| 2.139.0 | 8 / 0 | |
| 2.138.1 | 8 / 0 | |
| 2.138.0 | 8 / 0 | |
| 2.137.0 | 8 / 0 | |
| 2.136.0 | 8 / 0 | |
| 2.135.0 | 8 / 0 | |
| 2.134.0 | 8 / 0 | |
| 2.133.0 | 8 / 0 | |
| 2.132.0 | 8 / 0 | |
| 2.131.0 | 8 / 0 | |
| 2.130.0 | 8 / 0 | |
| 2.129.0 | 8 / 0 | |
| 2.128.0 | 8 / 0 | |
| 2.127.1 | 8 / 0 | |
| 2.127.0 | 8 / 0 | |
| 2.126.0 | 8 / 0 | |
| 2.125.0 | 8 / 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.175.0
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.152.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.151.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.150.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.149.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.148.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.147.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.146.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.145.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.144.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.143.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.142.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.141.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.140.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.139.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.138.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.138.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.135.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.134.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.133.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.132.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.131.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.130.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.129.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.128.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.127.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.127.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.126.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.125.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.