node-opcua-service-discovery
pure nodejs OPCUA SDK - module service-discovery
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-opcua-binary-stream | AI (phantom-deps): Sibling monorepo package used via compiled output. | ai | |
| phantom-deps | phantom-dep:node-opcua-service-secure-channel | AI (phantom-deps): Sibling monorepo package, used via TS compiled output not statically scanned. | ai | |
| phantom-deps | phantom-dep:@types/bonjour | AI (phantom-deps): Type-only package, expected to be unimported. | ai | |
| phantom-deps | phantom-dep:node-opcua-nodeid | AI (phantom-deps): Sibling monorepo package, used via TS compiled output not statically scanned. | ai | |
| phantom-deps | phantom-dep:node-opcua-factory | AI (phantom-deps): Sibling monorepo package, used via TS compiled output not statically scanned. | ai | |
| phantom-deps | phantom-dep:node-opcua-data-model | AI (phantom-deps): Sibling monorepo package, used via TS compiled output not statically scanned. | ai | |
| phantom-deps | phantom-dep:node-opcua-basic-types | AI (phantom-deps): Sibling monorepo package, used via TS compiled output not statically scanned. | ai | |
| phantom-deps | phantom-dep:node-opcua-service-endpoints | AI (phantom-deps): Sibling monorepo package, used via TS compiled output not statically scanned. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation confirms legitimate automated publishing. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from erossignon to GitHub Actions CI/CD is confirmed by SLSA attestation; stable for this monorepo package. | ai |
Versions (showing 100 of 181)
| Version | Deps | Published |
|---|---|---|
| 2.175.2 | 6 / 1 | |
| 2.175.1 | 6 / 1 | |
| 2.174.0 | 6 / 1 | |
| 2.173.0 | 6 / 1 | |
| 2.172.0 | 6 / 1 | |
| 2.170.0 | 6 / 1 | |
| 2.169.0 | 6 / 1 | |
| 2.168.0 | 6 / 1 | |
| 2.167.0 | 6 / 1 | |
| 2.165.0 | 6 / 1 | |
| 2.164.0 | 6 / 1 | |
| 2.163.1 | 6 / 1 | |
| 2.163.0 | 6 / 1 | |
| 2.162.0 | 6 / 1 | |
| 2.161.0 | 6 / 1 | |
| 2.159.0 | 6 / 1 | |
| 2.158.0 | 6 / 1 | |
| 2.157.0 | 6 / 1 | |
| 2.155.0 | 6 / 0 | |
| 2.154.0 | 6 / 0 | |
| 2.153.0 | 6 / 0 | |
| 2.151.0 | 6 / 0 | |
| 2.150.0 | 6 / 0 | |
| 2.143.0 | 6 / 0 | |
| 2.142.0 | 6 / 0 | |
| 2.141.0 | 6 / 0 | |
| 2.139.0 | 6 / 0 | |
| 2.137.0 | 6 / 0 | |
| 2.134.0 | 6 / 0 | |
| 2.133.0 | 6 / 0 | |
| 2.132.0 | 6 / 0 | |
| 2.131.0 | 6 / 0 | |
| 2.129.0 | 6 / 0 | |
| 2.128.0 | 6 / 0 | |
| 2.126.0 | 6 / 0 | |
| 2.125.0 | 6 / 0 | |
| 2.123.0 | 6 / 0 | |
| 2.121.0 | 6 / 0 | |
| 2.120.0 | 6 / 0 | |
| 2.119.2 | 6 / 0 | |
| 2.119.0 | 6 / 0 | |
| 2.118.0 | 6 / 0 | |
| 2.117.0 | 6 / 0 | |
| 2.114.0 | 6 / 0 | |
| 2.113.0 | 6 / 0 | |
| 2.112.0 | 6 / 0 | |
| 2.111.0 | 6 / 0 | |
| 2.110.0 | 6 / 0 | |
| 2.109.0 | 6 / 0 | |
| 2.108.0 | 6 / 0 | |
| 2.107.0 | 6 / 0 | |
| 2.105.0 | 6 / 0 | |
| 2.104.0 | 6 / 0 | |
| 2.103.0 | 6 / 0 | |
| 2.102.0 | 6 / 0 | |
| 2.101.0 | 6 / 0 | |
| 2.99.0 | 6 / 0 | |
| 2.98.2 | 6 / 0 | |
| 2.98.1 | 6 / 0 | |
| 2.98.0 | 6 / 0 | |
| 2.97.0 | 6 / 0 | |
| 2.96.0 | 6 / 0 | |
| 2.95.0 | 6 / 0 | |
| 2.92.0 | 6 / 0 | |
| 2.90.1 | 6 / 0 | |
| 2.90.0 | 6 / 0 | |
| 2.89.0 | 6 / 0 | |
| 2.88.0 | 6 / 0 | |
| 2.87.0 | 6 / 0 | |
| 2.86.1 | 6 / 0 | |
| 2.86.0 | 6 / 0 | |
| 2.85.0 | 6 / 0 | |
| 2.84.0 | 6 / 0 | |
| 2.83.0 | 6 / 0 | |
| 2.82.0 | 6 / 0 | |
| 2.81.0 | 6 / 0 | |
| 2.79.0 | 6 / 0 | |
| 2.78.0 | 6 / 0 | |
| 2.77.0 | 6 / 0 | |
| 2.76.2 | 6 / 0 | |
| 2.76.0 | 6 / 0 | |
| 2.75.0 | 13 / 0 | |
| 2.74.0 | 13 / 0 | |
| 2.73.1 | 13 / 0 | |
| 2.73.0 | 13 / 0 | |
| 2.72.2 | 13 / 0 | |
| 2.72.1 | 13 / 0 | |
| 2.72.0 | 13 / 0 | |
| 2.71.0 | 13 / 0 | |
| 2.70.3 | 13 / 0 | |
| 2.70.2 | 13 / 0 | |
| 2.70.0 | 13 / 0 | |
| 2.69.0 | 13 / 0 | |
| 2.68.1 | 13 / 0 | |
| 2.68.0 | 13 / 0 | |
| 2.67.0 | 13 / 0 | |
| 2.66.0 | 13 / 0 | |
| 2.65.1 | 13 / 0 | |
| 2.65.0 | 13 / 0 | |
| 2.64.1 | 13 / 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.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.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.139.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.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.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.126.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.123.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.121.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.120.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.113.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.112.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.110.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.109.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.86.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.