@taskforge-ai/worker
Polling worker that processes Jira tickets through the spec → approval → implementation FSM.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@anthropic-ai/sdk | AI (phantom-deps): Direct runtime dependency for worker implementation; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@anthropic-ai/claude-code | AI (phantom-deps): Direct runtime dependency for worker implementation; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@taskforge-ai/github-client | AI (phantom-deps): Direct runtime dependency; same-org scoped package is expected pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 6 / 3 | |
| 0.1.3 | 6 / 3 | |
| 0.1.2 | 6 / 3 | |
| 0.1.1 | 6 / 3 | |
| 0.1.0 | 6 / 3 |
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.