updated 2026-09-29 16:10 UTC

Tau

Repository Website by huggingface

A Python port of Pi’s minimalist coding agent.

Coding Agents Python Listed MIT

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

OSSF Scorecard No result
Provenance None
Signed commits 92%
Last push today
Advisories None known
Compare Tau

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Tau scores 39.7/100 (Grade D), ranked #1177 of 1343 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 92% of recent commits are signed; no published advisory affects its latest release (tau-ai); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Tau 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.

Already done? Suggest a correctionAdd the trust badge

How Tau compares in Coding Agents

  1. #63 GPT Pilot 39.9 +0.2
  2. #64 RA.Aid 39.8 +0.1
  3. #65 Tau 39.7 this agent
  4. #66 Plandex 33.5 −6.2
  5. #67 Continue 33.2 −6.5

Bars show each HVTrust score; the tick marks Tau’s 39.7.

Where the 39.7 comes from

HVTrust dimensions vs the Coding Agents average

39.7 / 100 · 67.0% confidence

Tau Coding Agents average (75 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.6 / 25
4.4 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.2 below avg 11.7
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
3.4 above avg 14.9
AdoptionLog-scaled stars · package downloads
12.2 / 20
in line with avg 12.2

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-29
Newly Listed
First tracked at rank #1177
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Tau View Coding Agents Report missing data
77.3
Activity sub-score · out of 100
#65
In Coding Agents

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 →

Signals refreshed 2026-09-29 16:10 UTC · Repo last pushed today

Activity & Reach

Stars
2.9k
Forks
365
Last Push
2026-09-29
today
Commits (4 wk)
36
Downloads (7d)
802
pypi
HN mentions (30d)
—
Open Issues
58
Rank Change
NEW

Analysis

Activity Inputs

77.3 / 100
StarsRepository reach
20.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
19.6 / 25
CommunityFork signal
11.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
92%
of last 100 commits verified

Common questions about Tau

Public trust evidence for Tau 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 Tau publish package provenance?
No published build provenance is currently detected for Tau. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Tau have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Tau. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Tau actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Tau use?
Tau ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Tau's commits signed?
92% of the last 100 commits to Tau 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Tau?

For maintainers

HVTrust scores Tau 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
Listed 1
2026-09-29
Newly Listed
First tracked at rank #1177
GitHub → Website → PyPI: tau-ai

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 39.7 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/tau.svg)](https://hvtracker.net/agents/tau)
HTML:
<a href="https://hvtracker.net/agents/tau"><img src="https://hvtracker.net/badge/tau.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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