@sidequest/engine
37
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
merenciagiovaniguizzo
Keywords
nodejsjavascripttypescriptqueueconcurrencybackground-jobsdistributedbackground
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is consistent with CI/CD automation for this established monorepo project. | ai | |
| dependencies | unvetted-dep:@sidequest/core | AI (dependencies): Sibling package in the same sidequest monorepo; unvetted status is expected for the whole suite. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; absence of Sigstore attestation is common and not a risk signal for this package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.16.2 | 4 / 0 | |
| 1.16.1 | 4 / 0 | |
| 1.16.0 | 4 / 0 | |
| 1.15.1 | 4 / 0 | |
| 1.15.0 | 4 / 0 | |
| 1.14.1 | 4 / 0 | |
| 1.14.0 | 4 / 0 | |
| 1.13.7 | 4 / 0 | |
| 1.13.6 | 4 / 0 | |
| 1.13.5 | 4 / 0 | |
| 1.13.4 | 4 / 0 | |
| 1.13.3 | 4 / 0 | |
| 1.13.2 | 4 / 0 | |
| 1.13.1 | 4 / 0 | |
| 1.13.0 | 4 / 0 | |
| 1.12.0 | 4 / 0 | |
| 1.11.0 | 4 / 0 | |
| 1.10.0 | 4 / 0 | |
| 1.9.0 | 4 / 0 | |
| 1.8.0 | 4 / 0 | |
| 1.7.1 | 4 / 0 | |
| 1.7.0 | 4 / 0 | |
| 1.6.2 | 4 / 0 | |
| 1.6.1 | 4 / 0 | |
| 1.6.0 | 4 / 0 | |
| 1.5.2 | 4 / 0 | |
| 1.5.1 | 4 / 0 | |
| 1.5.0 | 4 / 0 | |
| 1.4.3 | 4 / 0 | |
| 1.4.2 | 4 / 0 | |
| 1.4.1 | 4 / 0 | |
| 1.4.0 | 4 / 0 | |
| 1.3.0 | 4 / 0 | |
| 1.2.0 | 4 / 0 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 4 / 0 | |
| 1.0.0 | 4 / 0 |
v1.16.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.