@emartech/program-executor
Program executor is a scalable, resilient job framework that is capable of concurrently executing programs, while jobs inside a program are executed in order. Execution can be distributed between resources (multiple workers/threads). It is fault tolerant
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@emartech/json-logger | AI (dependencies): Internal Emartech org dependency; consistent with this package's ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@emartech/rabbitmq-client | AI (dependencies): Internal Emartech org dependency; consistent with this package's ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@emartech/pubsub-client-js | AI (dependencies): Internal Emartech org dependency; consistent with this package's ecosystem pattern. | ai | |
| provenance | no-provenance | AI (provenance): Org-internal package with consistent publish history; lack of Sigstore provenance is expected for this publisher. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.19.2 | 5 / 9 | |
| 3.19.1 | 5 / 9 | |
| 3.19.0 | 5 / 9 | |
| 3.18.0 | 5 / 9 | |
| 3.16.1 | 5 / 9 | |
| 3.16.0 | 5 / 9 | |
| 3.12.1 | 5 / 9 | |
| 3.11.1 | 4 / 16 | |
| 3.11.0 | 3 / 16 | |
| 3.10.0 | 3 / 16 |
v3.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
v3.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.