← Home

@convex-dev/workflow

21
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

cowlingjordanhuntgautamg795emmaling27nipunnaritrakhianatconvexdowski-convexreece-convexerquhartsethconvexjamwtnicolapps

Keywords

convexworkflowdurable-execution

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 21 of 21)

Version Deps Published
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

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.