@tryghost/job-manager
A manager for background jobs in Ghost, supporting one-off tasks and recurring jobs.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:bree | AI (dependencies): bree is a documented, intentional core dependency of this job-manager package; stable across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Job-dispatch pattern in a job manager; job path is caller-controlled, not external user input. Stable across versions. | ai | |
| phantom-deps | phantom-dep:workerpool | AI (phantom-deps): workerpool is a declared runtime dep; phantom-dep heuristic fires incorrectly here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 8 / 4 | |
| 3.1.1 | 8 / 4 | |
| 3.1.0 | 8 / 4 | |
| 3.0.3 | 8 / 4 | |
| 3.0.2 | 8 / 4 | |
| 3.0.1 | 8 / 4 | |
| 3.0.0 | 8 / 6 | |
| 2.2.1 | 8 / 7 | |
| 2.2.0 | 8 / 7 | |
| 2.1.0 | 8 / 7 | |
| 2.0.0 | 8 / 7 | |
| 1.0.9 | 8 / 7 | |
| 1.0.8 | 8 / 7 | |
| 1.0.7 | 8 / 7 | |
| 1.0.6 | 8 / 8 | |
| 1.0.5 | 8 / 8 | |
| 1.0.4 | 8 / 8 |
v3.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.