@openfn/ws-worker
A Websocket Worker to connect Lightning to a Runtime Engine
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@openfn/logger | AI (dependencies): First-party @openfn scoped package; stable across all versions of this monorepo. | ai | |
| dependencies | unvetted-dep:@openfn/lexicon | AI (dependencies): First-party @openfn scoped package; stable across all versions of this monorepo. | ai | |
| dependencies | unvetted-dep:@types/koa-logger | AI (dependencies): DefinitelyTyped type stub with no runtime code; no meaningful risk. | ai | |
| provenance | no-provenance | AI (provenance): Established openfn org package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Type-only package; not imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/koa-logger | AI (phantom-deps): Type-only package; not imported at runtime by convention. | ai |
Versions (showing 100 of 102)
| Version | Deps | Published |
|---|---|---|
| 1.27.2 | 17 / 14 | |
| 1.27.1 | 17 / 14 | |
| 1.27.0 | 17 / 14 | |
| 1.26.1 | 17 / 14 | |
| 1.26.0 | 17 / 14 | |
| 1.25.1 | 17 / 14 | |
| 1.25.0 | 17 / 14 | |
| 1.24.2 | 17 / 14 | |
| 1.24.1 | 17 / 14 | |
| 1.23.8 | 17 / 14 | |
| 1.23.4 | 17 / 14 | |
| 1.23.3 | 17 / 14 | |
| 1.23.2 | 17 / 14 | |
| 1.23.1 | 17 / 14 | |
| 1.23.0 | 17 / 14 | |
| 1.22.2 | 17 / 15 | |
| 1.22.1 | 17 / 15 | |
| 1.22.0 | 17 / 15 | |
| 1.21.5 | 17 / 15 | |
| 1.21.4 | 17 / 15 | |
| 1.21.3 | 17 / 15 | |
| 1.21.2 | 17 / 15 | |
| 1.21.1 | 17 / 15 | |
| 1.21.0 | 17 / 15 | |
| 1.20.2 | 17 / 15 | |
| 1.20.1 | 17 / 15 | |
| 1.20.0 | 17 / 15 | |
| 1.19.7 | 17 / 15 | |
| 1.19.6 | 17 / 15 | |
| 1.19.5 | 17 / 15 | |
| 1.19.3 | 17 / 15 | |
| 1.19.2 | 17 / 15 | |
| 1.19.1 | 17 / 15 | |
| 1.19.0 | 17 / 15 | |
| 1.18.1 | 17 / 15 | |
| 1.18.0 | 17 / 15 | |
| 1.17.0 | 17 / 15 | |
| 1.16.1 | 17 / 15 | |
| 1.16.0 | 17 / 15 | |
| 1.15.4 | 17 / 15 | |
| 1.15.3 | 17 / 15 | |
| 1.15.2 | 17 / 15 | |
| 1.15.1 | 17 / 15 | |
| 1.15.0 | 17 / 15 | |
| 1.14.5 | 17 / 15 | |
| 1.14.4 | 17 / 15 | |
| 1.14.3 | 17 / 15 | |
| 1.14.2 | 17 / 15 | |
| 1.14.1 | 17 / 15 | |
| 1.14.0 | 17 / 15 | |
| 1.13.6 | 17 / 15 | |
| 1.13.5 | 17 / 15 | |
| 1.13.4 | 17 / 15 | |
| 1.13.3 | 17 / 15 | |
| 1.13.2 | 17 / 15 | |
| 1.13.1 | 17 / 15 | |
| 1.13.0 | 17 / 15 | |
| 1.12.1 | 16 / 14 | |
| 1.12.0 | 16 / 14 | |
| 1.11.1 | 16 / 14 | |
| 1.11.0 | 16 / 14 | |
| 1.10.0 | 16 / 14 | |
| 1.9.2 | 16 / 14 | |
| 1.9.1 | 16 / 14 | |
| 1.9.0 | 16 / 14 | |
| 1.8.9 | 16 / 14 | |
| 1.8.6 | 16 / 15 | |
| 1.8.5 | 16 / 15 | |
| 1.8.4 | 16 / 15 | |
| 1.8.3 | 16 / 15 | |
| 1.8.2 | 16 / 15 | |
| 1.8.1 | 16 / 15 | |
| 1.8.0 | 16 / 15 | |
| 1.7.0 | 16 / 15 | |
| 1.6.7 | 16 / 15 | |
| 1.6.6 | 16 / 15 | |
| 1.6.4 | 16 / 15 | |
| 1.6.3 | 16 / 15 | |
| 1.6.2 | 16 / 15 | |
| 1.6.1 | 16 / 15 | |
| 1.6.0 | 16 / 15 | |
| 1.5.1 | 16 / 15 | |
| 1.5.0 | 16 / 15 | |
| 1.4.1 | 16 / 15 | |
| 1.4.0 | 16 / 15 | |
| 1.3.0 | 16 / 15 | |
| 1.2.2 | 16 / 15 | |
| 1.2.1 | 16 / 15 | |
| 1.2.0 | 16 / 15 | |
| 1.1.11 | 16 / 15 | |
| 1.1.10 | 16 / 15 | |
| 1.1.9 | 16 / 15 | |
| 1.1.8 | 16 / 15 | |
| 1.1.7 | 16 / 15 | |
| 1.1.6 | 16 / 15 | |
| 1.1.5 | 16 / 15 | |
| 1.1.4 | 16 / 15 | |
| 1.1.3 | 16 / 15 | |
| 1.1.2 | 16 / 15 | |
| 1.1.1 | 16 / 15 |
v1.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.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.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.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.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.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.
v1.10.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.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.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.
v1.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.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.
v1.7.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.
v1.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.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.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.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.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.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.
v1.3.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.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.