@convex-dev/workflow
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher is part of the Convex org with 14 approved packages; internal team handoff, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Convex org package with legitimate publisher history; dormancy reflects development cadence, not account compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers follow convex org naming convention; consistent with internal team expansion, not takeover. | ai | |
| dependencies | unvetted-peer-dep:@convex-dev/workpool | AI (dependencies): Internal Convex ecosystem peer dep; stable across versions. | ai | |
| dependencies | unvetted-dep:async-channel | AI (dependencies): async-channel is a legitimate async utility; no malicious indicators for this package's use. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.4.4 | 1 / 25 | |
| 0.4.3 | 1 / 25 | |
| 0.4.2 | 1 / 25 | |
| 0.4.1 | 1 / 25 | |
| 0.3.12 | 1 / 24 | |
| 0.3.11 | 1 / 24 | |
| 0.3.10 | 1 / 24 | |
| 0.3.9 | 1 / 24 | |
| 0.3.8 | 1 / 24 | |
| 0.3.7 | 1 / 24 | |
| 0.3.6 | 1 / 24 | |
| 0.3.5 | 1 / 24 | |
| 0.3.4 | 1 / 24 | |
| 0.3.3 | 1 / 23 | |
| 0.3.2 | 1 / 23 | |
| 0.3.1 | 1 / 23 | |
| 0.3.0 | 1 / 23 | |
| 0.2.7 | 1 / 20 | |
| 0.2.6 | 1 / 18 | |
| 0.2.5 | 1 / 18 | |
| 0.2.4 | 1 / 12 | |
| 0.2.3 | 1 / 12 | |
| 0.2.2 | 1 / 12 | |
| 0.2.1 | 1 / 12 | |
| 0.2.0 | 1 / 12 | |
| 0.1.5 | 1 / 11 | |
| 0.1.4 | 1 / 11 | |
| 0.1.3 | 1 / 11 | |
| 0.1.2 | 2 / 11 | |
| 0.1.1 | 2 / 11 |
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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-04-05, 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.5
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 (sujayakar) 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.4
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 (sujayakar) on 2025-01-14, 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.