@openfn/engine-multi
Multi-process 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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established org package with clean publisher history; gap likely reflects normal release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@openfn/logger | AI (dependencies): Same-org @openfn/* dependency; consistent with monorepo structure across all versions. | ai | |
| dependencies | unvetted-dep:@openfn/lexicon | AI (dependencies): Same-org @openfn/* dependency; consistent with monorepo structure across all versions. | ai | |
| dependencies | unvetted-dep:@openfn/compiler | AI (dependencies): Same-org @openfn/* dependency; consistent with monorepo structure across all versions. | ai | |
| phantom-deps | phantom-dep:@openfn/lexicon | AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires on indirect/type-only usage common in monorepos. | ai | |
| phantom-deps | phantom-dep:@openfn/language-common | AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires on indirect/type-only usage common in monorepos. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 7 / 7 | |
| 1.12.1 | 7 / 7 | |
| 1.12.0 | 7 / 7 | |
| 1.11.4 | 7 / 7 | |
| 1.11.3 | 7 / 7 | |
| 1.11.2 | 7 / 7 | |
| 1.11.1 | 7 / 7 | |
| 1.11.0 | 7 / 7 | |
| 1.10.8 | 7 / 7 | |
| 1.10.7 | 7 / 7 | |
| 1.10.6 | 7 / 7 | |
| 1.10.5 | 7 / 7 | |
| 1.10.4 | 7 / 7 | |
| 1.10.3 | 7 / 7 | |
| 1.10.2 | 7 / 7 | |
| 1.10.1 | 7 / 7 | |
| 1.10.0 | 7 / 7 | |
| 1.9.1 | 7 / 7 | |
| 1.9.0 | 7 / 7 | |
| 1.8.5 | 6 / 7 | |
| 1.8.4 | 6 / 7 | |
| 1.8.3 | 6 / 7 | |
| 1.8.2 | 6 / 7 | |
| 1.8.1 | 6 / 7 | |
| 1.8.0 | 6 / 7 | |
| 1.7.1 | 6 / 7 | |
| 1.7.0 | 6 / 7 | |
| 1.6.14 | 6 / 7 | |
| 1.6.13 | 6 / 7 | |
| 1.6.12 | 6 / 7 | |
| 1.6.11 | 6 / 7 | |
| 1.6.10 | 6 / 7 | |
| 1.6.9 | 6 / 7 | |
| 1.6.8 | 6 / 7 | |
| 1.6.7 | 6 / 7 | |
| 1.6.6 | 6 / 7 | |
| 1.6.5 | 6 / 7 | |
| 1.6.4 | 6 / 6 | |
| 1.6.3 | 6 / 6 | |
| 1.6.2 | 6 / 6 | |
| 1.6.1 | 6 / 6 | |
| 1.6.0 | 6 / 6 | |
| 1.5.1 | 6 / 6 | |
| 1.5.0 | 6 / 6 | |
| 1.4.9 | 6 / 6 | |
| 1.4.8 | 6 / 6 | |
| 1.4.7 | 6 / 6 | |
| 1.4.6 | 6 / 6 | |
| 1.4.5 | 6 / 7 | |
| 1.4.4 | 6 / 7 | |
| 1.4.3 | 6 / 7 |
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.