@convex-dev/workpool
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@edge-runtime/vm | AI (phantom-deps): Test/runtime tooling loaded by convention, not a direct import concern. | ai | |
| phantom-deps | phantom-dep:@vitest/coverage-v8 | AI (phantom-deps): Standard vitest coverage plugin, loaded by framework convention. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jamwt is a known Convex org member; publisher change already flagged as known maintainer. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.4.8 | 0 / 28 | |
| 0.4.7 | 0 / 26 | |
| 0.4.6 | 0 / 27 | |
| 0.4.5 | 0 / 27 | |
| 0.4.4 | 0 / 27 | |
| 0.4.3 | 0 / 27 | |
| 0.4.2 | 0 / 27 | |
| 0.4.1 | 0 / 27 | |
| 0.4.0 | 0 / 27 | |
| 0.3.2 | 0 / 27 | |
| 0.3.1 | 0 / 26 | |
| 0.3.0 | 0 / 26 | |
| 0.2.19 | 0 / 25 | |
| 0.2.18 | 0 / 12 | |
| 0.2.17 | 0 / 12 | |
| 0.2.16 | 0 / 12 | |
| 0.2.15 | 0 / 11 | |
| 0.2.14 | 0 / 11 | |
| 0.2.13 | 0 / 11 | |
| 0.2.12 | 0 / 11 | |
| 0.2.11 | 0 / 11 | |
| 0.2.10 | 0 / 11 | |
| 0.2.9 | 0 / 11 | |
| 0.2.8 | 0 / 11 | |
| 0.2.7 | 0 / 11 | |
| 0.2.6 | 0 / 11 | |
| 0.2.5 | 0 / 11 | |
| 0.2.4 | 0 / 11 | |
| 0.2.3 | 0 / 11 | |
| 0.2.2 | 0 / 11 | |
| 0.2.1 | 0 / 11 | |
| 0.2.0 | 2 / 9 | |
| 0.1.2 | 1 / 9 | |
| 0.1.1 | 1 / 9 | |
| 0.1.0 | 1 / 9 |
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (reece-convex) than the most recent previously approved version (ianatconvex) on 2026-03-21, but reece-convex is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ianatconvex) than the most recent previously approved version (ballingt) on 2025-03-11, but ianatconvex is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ianatconvex) than the most recent previously approved version (ballingt) on 2025-03-08, but ianatconvex is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ballingt) than the most recent previously approved version (ldanilek) on 2025-02-05, but ballingt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.