@openfn/runtime
Job processing runtime.
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 sibling package from the same OpenFn org; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established OpenFn org package; lack of provenance is consistent across their published versions. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is a declared runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.9.5 | 5 / 13 | |
| 1.9.4 | 5 / 13 | |
| 1.9.3 | 5 / 13 | |
| 1.9.2 | 5 / 13 | |
| 1.9.1 | 5 / 13 | |
| 1.9.0 | 5 / 13 | |
| 1.8.7 | 5 / 13 | |
| 1.8.6 | 5 / 13 | |
| 1.8.5 | 5 / 13 | |
| 1.8.4 | 5 / 13 | |
| 1.8.3 | 5 / 13 | |
| 1.8.2 | 5 / 13 | |
| 1.8.1 | 5 / 13 | |
| 1.8.0 | 5 / 13 | |
| 1.7.7 | 4 / 13 | |
| 1.7.6 | 4 / 13 | |
| 1.7.5 | 4 / 13 | |
| 1.7.4 | 4 / 13 | |
| 1.7.3 | 4 / 13 | |
| 1.7.2 | 4 / 13 | |
| 1.7.1 | 4 / 13 | |
| 1.7.0 | 4 / 13 | |
| 1.6.4 | 4 / 13 | |
| 1.6.3 | 4 / 13 | |
| 1.6.2 | 4 / 13 | |
| 1.6.1 | 4 / 13 | |
| 1.6.0 | 4 / 13 | |
| 1.5.4 | 3 / 10 | |
| 1.5.3 | 3 / 11 | |
| 1.5.2 | 3 / 11 | |
| 1.5.1 | 3 / 11 | |
| 1.5.0 | 3 / 11 | |
| 1.4.2 | 3 / 11 | |
| 1.4.1 | 3 / 11 | |
| 1.4.0 | 3 / 11 | |
| 1.3.0 | 3 / 11 | |
| 1.2.0 | 3 / 11 | |
| 1.1.3 | 3 / 11 | |
| 1.1.2 | 3 / 11 | |
| 1.1.1 | 3 / 11 | |
| 1.1.0 | 3 / 11 | |
| 1.0.0 | 3 / 11 |
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.0.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.