Is Subtask safe to use?

Subtask has an HVTrust score of 32.3/100 (Grade D), ranked #353 of 371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Subtask?

Subtask scores 32.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 338 GitHub stars and is categorized under Agent Skills.

Subtask

Repository

Claude Skill to do your tasks with subagents in Git worktrees

Agent Skills Go Listed MIT

Is Subtask safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.4 / 10

Provenance None

Signed commits 26%

Last push 166d ago

Compare Subtask

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Subtask scores 32.3/100 (Grade D), ranked #353 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.4/10; 26% of recent commits are signed; last pushed 2026-04-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How Subtask could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 2.4 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +13.8 → 46.1 D · #284 of 371
Sign every commit26% signed today +3.7 → 36.0 D · #346 of 371

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Subtask and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

Source Partly signed

github.com/zippoxer/subtask, MIT, last pushed 2026-04-27. 26% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.4/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. Subtask is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-30 OSSF Scorecard: 2.4/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Subtask’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Subtask compares in Agent Skills

Bars show each HVTrust score; the tick marks Subtask’s 32.3.

Where the 32.3 comes from

HVTrust dimensions vs the Agent Skills average

32.3 / 100 · 100.0% confidence

Subtask Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.3 / 25

3.5 below avg 7.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

10.5 / 17

1.5 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

0.9 / 20

13.2 below avg 14.1

AdoptionLog-scaled stars · package downloads

6.1 / 20

2.9 below avg 9.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 16 spots (#324 → #340)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 166 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Subtask View Agent Skills Report missing data

24.2

Activity sub-score · out of 100

#353

In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars

338

Forks

Last Push

2026-04-27

166 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #349

Analysis

Activity Inputs

24.2 / 100

StarsRepository reach

15.2 / 30

FreshnessLast push recency

1.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

6.9 / 20

Common questions about Subtask

Public trust evidence for Subtask is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Subtask publish package provenance?

No published build provenance is currently detected for Subtask. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Subtask have an OpenSSF Scorecard?

Subtask has an OpenSSF Scorecard score of 2.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Subtask actively maintained?

Slowing down. Last push was 166 days ago — keep an eye on whether activity resumes.

What license does Subtask use?

Subtask ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Subtask's commits signed?

25% of the last 100 commits to Subtask are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Subtask's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintain Subtask?

For maintainers

HVTrust scores Subtask from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 16 spots (#324 → #340)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

HVTrust Changed

HVTrust up 9.5pts (24.0 → 33.5)

2026-09-22

Newly Listed

First tracked at rank #317

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-10

Rank Moved

Rank dropped 10 spots (#297 → #307)

2026-09-05

Rank Moved

Rank dropped 10 spots (#266 → #276)

2026-09-03

Rank Moved

Rank dropped 13 spots (#247 → #260)

2026-09-02

Rank Moved

Rank dropped 13 spots (#234 → #247)

2026-09-01

Rank Moved

Rank dropped 14 spots (#220 → #234)

2026-08-31

Rank Moved

Rank dropped 17 spots (#203 → #220)

2026-08-30

Scorecard Added

OSSF Scorecard: 2.4/10

2026-08-30

Rank Moved

Rank rose 109 spots (#312 → #203)

2026-08-30

HVTrust Changed

HVTrust up 20.2pts (14.9 → 35.1)

2026-08-26

Newly Listed

First tracked at rank #304

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/subtask.svg)](https://hvtracker.net/agents/subtask)
            
HTML:
            <a href="https://hvtracker.net/agents/subtask"><img src="https://hvtracker.net/badge/subtask.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Subtask

How Subtask could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Subtask compares in Agent Skills

Where the 32.3 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Subtask

AI agent surface

Maintain Subtask?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills