@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 — the axios compromise (March 2026) relied on exactly this gap.
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 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.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.14.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.14.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.14.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.13.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.13.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.13.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.