node-opcua-alarm-condition
pure nodejs OPCUA SDK - module pseudo-session
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from erossignon to GitHub Actions CI/CD is documented by SLSA provenance attestation; legitimate org-level automation change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration with SLSA attestation; consistent with a legitimate release pipeline overhaul. | ai | |
| dependencies | unvetted-dep:node-opcua-variant | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-data-model | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-basic-types | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-status-code | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-types | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-pseudo-session | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-service-filter | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-service-subscription | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-service-translate-browse-path | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-service-read | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai | |
| dependencies | unvetted-dep:node-opcua-nodeid | AI (dependencies): Sibling package in the node-opcua monorepo; same publisher and release cadence. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.175.2 | 16 / 0 | |
| 2.175.1 | 16 / 0 | |
| 2.174.0 | 16 / 0 | |
| 2.173.0 | 16 / 0 | |
| 2.172.0 | 16 / 0 | |
| 2.170.1 | 16 / 0 | |
| 2.169.0 | 16 / 0 | |
| 2.168.0 | 16 / 0 | |
| 2.167.0 | 16 / 0 | |
| 2.166.0 | 16 / 0 | |
| 2.165.2 | 16 / 0 | |
| 2.165.1 | 16 / 0 | |
| 2.165.0 | 16 / 0 | |
| 2.164.2 | 16 / 0 | |
| 2.163.1 | 16 / 0 | |
| 2.163.0 | 16 / 0 | |
| 2.162.0 | 16 / 0 | |
| 2.161.0 | 16 / 0 | |
| 2.160.0 | 16 / 0 | |
| 2.159.0 | 16 / 0 | |
| 2.158.0 | 16 / 0 | |
| 2.157.0 | 16 / 0 | |
| 2.156.0 | 17 / 0 | |
| 2.155.0 | 17 / 0 | |
| 2.154.0 | 17 / 0 | |
| 2.153.0 | 17 / 0 | |
| 2.152.0 | 17 / 0 | |
| 2.151.0 | 17 / 0 | |
| 2.150.0 | 17 / 0 | |
| 2.149.0 | 17 / 0 | |
| 2.143.0 | 17 / 0 | |
| 2.142.0 | 17 / 0 | |
| 2.141.0 | 17 / 0 | |
| 2.140.0 | 17 / 0 | |
| 2.139.0 | 17 / 0 | |
| 2.138.0 | 17 / 0 | |
| 2.137.0 | 17 / 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.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
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (erossignon) on 2026-01-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.159.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.158.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.157.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.156.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.155.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.154.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.153.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.152.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.140.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.137.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.