@constructive-io/job-scheduler
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with strong track record; absence of provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 2.16.2 | 4 / 1 | |
| 2.16.1 | 4 / 1 | |
| 2.16.0 | 4 / 1 | |
| 2.15.0 | 4 / 1 | |
| 2.14.6 | 4 / 1 | |
| 2.14.5 | 4 / 1 | |
| 2.14.4 | 4 / 1 | |
| 2.14.3 | 4 / 1 | |
| 2.14.2 | 4 / 1 | |
| 2.14.1 | 4 / 1 | |
| 2.14.0 | 4 / 1 | |
| 2.13.1 | 4 / 1 | |
| 2.13.0 | 4 / 1 | |
| 2.12.1 | 4 / 1 | |
| 2.12.0 | 4 / 1 | |
| 2.11.1 | 4 / 1 | |
| 2.11.0 | 4 / 1 | |
| 2.10.1 | 4 / 1 | |
| 2.10.0 | 4 / 1 | |
| 2.9.0 | 4 / 1 | |
| 2.8.0 | 4 / 1 | |
| 2.7.0 | 4 / 1 | |
| 2.6.0 | 4 / 1 | |
| 2.5.4 | 4 / 1 | |
| 2.5.3 | 4 / 1 | |
| 2.5.2 | 4 / 1 | |
| 2.5.1 | 4 / 1 | |
| 2.5.0 | 4 / 1 | |
| 2.4.4 | 4 / 1 | |
| 2.4.3 | 4 / 1 | |
| 2.4.2 | 4 / 1 | |
| 2.2.1 | 4 / 1 | |
| 2.2.0 | 4 / 1 | |
| 2.1.0 | 4 / 1 | |
| 2.0.1 | 4 / 1 | |
| 2.0.0 | 4 / 1 | |
| 1.1.0 | 4 / 1 | |
| 1.0.0 | 4 / 1 | |
| 0.5.1 | 4 / 1 | |
| 0.5.0 | 4 / 1 | |
| 0.4.1 | 4 / 1 | |
| 0.4.0 | 4 / 0 | |
| 0.3.22 | 4 / 0 | |
| 0.3.21 | 4 / 0 | |
| 0.3.20 | 4 / 0 | |
| 0.3.19 | 4 / 0 | |
| 0.3.18 | 4 / 0 | |
| 0.3.17 | 4 / 0 | |
| 0.3.16 | 4 / 0 | |
| 0.3.15 | 4 / 0 | |
| 0.3.14 | 4 / 0 |
v2.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.