node-opcua-server
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 personal account to GitHub Actions CI is a documented, legitimate migration for this established package; SLSA attestation confirms integrity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 338 versions over 3172 days; any gap is consistent with normal release cadence, not account takeover. | ai | |
| phantom-deps | phantom-dep:@types/async | AI (phantom-deps): TypeScript type package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): TypeScript type package; not directly imported at runtime by convention. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo with 130+ sub-packages; templated naming and link-dump README are expected for this SDK family. | ai | |
| phantom-deps | phantom-dep:node-opcua-pki | AI (phantom-deps): node-opcua-pki is a legitimate dependency used via config/indirect references in this monorepo package. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 2.175.2 | 49 / 5 | |
| 2.175.1 | 49 / 5 | |
| 2.175.0 | 49 / 5 | |
| 2.174.0 | 49 / 5 | |
| 2.173.1 | 49 / 5 | |
| 2.173.0 | 49 / 5 | |
| 2.172.0 | 49 / 5 | |
| 2.170.1 | 49 / 5 | |
| 2.169.0 | 49 / 5 | |
| 2.168.0 | 49 / 5 | |
| 2.167.0 | 51 / 3 | |
| 2.166.0 | 51 / 3 | |
| 2.165.2 | 51 / 3 | |
| 2.165.1 | 51 / 3 | |
| 2.165.0 | 51 / 3 | |
| 2.164.2 | 51 / 3 | |
| 2.163.1 | 51 / 3 | |
| 2.163.0 | 51 / 3 | |
| 2.162.0 | 51 / 3 | |
| 2.161.0 | 51 / 3 | |
| 2.160.0 | 51 / 3 | |
| 2.159.0 | 51 / 3 | |
| 2.158.0 | 51 / 3 | |
| 2.157.0 | 51 / 3 | |
| 2.156.0 | 49 / 3 | |
| 2.155.0 | 49 / 3 | |
| 2.154.0 | 49 / 3 | |
| 2.153.0 | 49 / 3 | |
| 2.152.0 | 49 / 3 | |
| 2.151.0 | 49 / 3 | |
| 2.150.0 | 49 / 3 | |
| 2.149.0 | 49 / 3 | |
| 2.148.0 | 49 / 3 | |
| 2.147.0 | 49 / 3 | |
| 2.146.0 | 49 / 3 | |
| 2.145.0 | 49 / 3 | |
| 2.144.0 | 49 / 3 | |
| 2.143.0 | 49 / 3 | |
| 2.142.0 | 49 / 3 | |
| 2.141.0 | 49 / 4 | |
| 2.140.0 | 49 / 4 | |
| 2.139.0 | 49 / 4 | |
| 2.138.1 | 49 / 4 | |
| 2.138.0 | 49 / 4 | |
| 2.137.0 | 49 / 4 | |
| 2.136.0 | 49 / 4 | |
| 2.135.0 | 49 / 4 | |
| 2.134.0 | 49 / 4 | |
| 2.133.0 | 49 / 4 | |
| 2.132.0 | 49 / 4 | |
| 2.131.0 | 49 / 4 | |
| 2.130.0 | 49 / 4 | |
| 2.129.0 | 49 / 4 | |
| 2.128.0 | 49 / 4 | |
| 2.127.1 | 49 / 6 | |
| 2.127.0 | 49 / 6 | |
| 2.126.0 | 49 / 6 | |
| 2.125.0 | 49 / 6 | |
| 2.105.1 | 48 / 6 | |
| 2.105.0 | 48 / 6 | |
| 2.104.0 | 48 / 6 | |
| 2.103.0 | 48 / 7 | |
| 2.102.0 | 48 / 7 | |
| 2.101.0 | 48 / 7 | |
| 2.100.0 | 48 / 7 | |
| 2.99.0 | 48 / 7 | |
| 2.98.2 | 48 / 7 | |
| 2.98.1 | 48 / 7 | |
| 2.98.0 | 48 / 7 | |
| 2.97.0 | 48 / 7 | |
| 2.96.0 | 48 / 7 | |
| 2.95.0 | 48 / 7 | |
| 2.94.0 | 48 / 7 | |
| 2.93.0 | 48 / 7 | |
| 2.92.0 | 48 / 7 | |
| 2.91.1 | 48 / 7 | |
| 2.91.0 | 48 / 7 | |
| 2.90.1 | 48 / 7 | |
| 2.90.0 | 48 / 7 | |
| 2.89.0 | 48 / 7 | |
| 2.88.0 | 48 / 7 | |
| 2.87.0 | 48 / 7 | |
| 2.86.1 | 48 / 7 | |
| 2.86.0 | 48 / 7 | |
| 2.85.0 | 48 / 7 | |
| 2.84.0 | 48 / 7 | |
| 2.83.0 | 48 / 7 | |
| 2.82.0 | 48 / 7 | |
| 2.81.0 | 48 / 7 | |
| 2.80.0 | 48 / 7 | |
| 2.79.1 | 48 / 7 | |
| 2.79.0 | 48 / 7 | |
| 2.78.0 | 48 / 7 | |
| 2.77.0 | 48 / 7 | |
| 2.76.2 | 48 / 7 |
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 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.148.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.147.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.146.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.145.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.144.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.1
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.136.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.135.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.130.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.127.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.127.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.105.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.105.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.103.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.76.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.