@taskforge-ai/cli
AI agent that implements tickets from Jira, and more
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @taskforge-ai/cli bears no semantic resemblance to joi; edit-distance match is coincidental. | ai | |
| phantom-deps | phantom-dep:@anthropic-ai/sdk | AI (phantom-deps): SDK likely used via config/wrapper pattern in a monorepo; not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@taskforge-ai/shared | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for internal shared packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.5 | 11 / 0 | |
| 0.1.4 | 11 / 0 | |
| 0.1.3 | 11 / 0 | |
| 0.1.2 | 11 / 0 | |
| 0.1.1 | 11 / 0 | |
| 0.1.0 | 11 / 0 |
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.