T3MP3ST

autonomous red teaming platform; multi-agent offensive-security meta-harness

Security & Guardrails TypeScript Grade C Listed AGPL-3.0
58.3/100
Rank #656 of 1328
Compare T3MP3ST

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-08 · 10d ago
Recent change
Rank

Is T3MP3ST safe? T3MP3ST scores 58.3/100 (Grade C), ranked #656 of 1328 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 4.1/10; 97% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-11
Rank Moved
Rank dropped 14 spots (#627 → #641)
2026-09-08
Rank Moved
Rank dropped 69 spots (#547 → #616)
2026-09-07
Rank Moved
Rank dropped 29 spots (#518 → #547)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/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.
80.4
Activity sub-score · out of 100
#8

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-18 13:03 UTC · Repo last pushed 10 days ago

Rank Trend

2026-08-11 2026-09-18

Activity & Reach

Stars
6.2k
Forks
1.3k
Last Push
2026-09-08
10 days ago
Commits (4 wk)
35
Downloads (7d)
HN mentions (30d)
Open Issues
4
Rank Change
▲1
was #657

Analysis

HVTrust Dimensions vs Security & Guardrails

58.3 / 100 · 100.0% confidence

T3MP3ST Security & Guardrails average (22 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.0 / 25
in line with avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
0.8 below avg 12.8
Maintenance60% last-push freshness · 40% commit activity
17.5 / 20
1.8 above avg 15.7
AdoptionLog-scaled stars · package downloads
9.1 / 20
0.8 below avg 9.9

Activity Inputs

80.4 / 100
StarsRepository reach
22.7 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
19.4 / 25
CommunityFork signal
14.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.1 / 10
OpenSSF Scorecard · scanned Sep 15, 2026
Signed Commits
97%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 9
CII-Best-Practices 0
Code-Review 1
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 4
SAST 0
Security-Policy 4
Signed-Releases 0
Token-Permissions 10
Vulnerabilities 5

Is T3MP3ST safe?

T3MP3ST has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does T3MP3ST publish package provenance?
No published build provenance is currently detected for T3MP3ST. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does T3MP3ST have an OpenSSF Scorecard?
T3MP3ST has an OpenSSF Scorecard score of 4.1/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 T3MP3ST actively maintained?
Maintained. Last push was 10 days ago.
What license does T3MP3ST use?
T3MP3ST ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are T3MP3ST's commits signed?
97% of the last 100 commits to T3MP3ST 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.

Compare T3MP3ST head-to-head

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
high confidence
Implemented
T3MP3ST appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
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

Maintain T3MP3ST?

For maintainers

HVTrust scores T3MP3ST 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.

Reputation Timeline

Signal history
Rank 23Listed 1HVTrust 1Grade 1Scorecard 1Score 1
2026-09-11
Rank Moved
Rank dropped 14 spots (#627 → #641)
2026-09-08
Rank Moved
Rank dropped 69 spots (#547 → #616)
2026-09-07
Rank Moved
Rank dropped 29 spots (#518 → #547)
2026-09-06
Rank Moved
Rank dropped 15 spots (#503 → #518)
2026-09-05
Rank Moved
Rank dropped 61 spots (#442 → #503)
2026-09-03
Rank Moved
Rank rose 46 spots (#495 → #449)
2026-09-03
Activity Score Changed
Activity score up 8pts (71 → 80)
2026-09-01
Rank Moved
Rank dropped 27 spots (#462 → #489)
2026-08-31
Rank Moved
Rank dropped 39 spots (#423 → #462)
2026-08-29
Rank Moved
Rank dropped 14 spots (#409 → #423)
2026-08-27
Rank Moved
Rank dropped 13 spots (#393 → #406)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.1/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 487 spots (#880 → #393)
2026-08-26
HVTrust Changed
HVTrust up 35.0pts (23.8 → 58.8)
2026-08-24
Rank Moved
Rank dropped 10 spots (#867 → #877)
2026-08-23
Rank Moved
Rank rose 30 spots (#897 → #867)
2026-08-22
Rank Moved
Rank rose 10 spots (#907 → #897)
2026-08-20
Rank Moved
Rank dropped 13 spots (#898 → #911)
2026-08-19
Rank Moved
Rank dropped 29 spots (#869 → #898)
2026-08-17
Rank Moved
Rank rose 12 spots (#881 → #869)
2026-08-16
Rank Moved
Rank dropped 29 spots (#852 → #881)
2026-08-15
Rank Moved
Rank dropped 14 spots (#838 → #852)
2026-08-13
Rank Moved
Rank dropped 12 spots (#821 → #833)
2026-08-12
Rank Moved
Rank rose 17 spots (#838 → #821)
2026-08-10
Rank Moved
Rank dropped 46 spots (#789 → #835)
2026-08-08
Rank Moved
Rank dropped 339 spots (#444 → #783)
2026-08-03
Newly Listed
First tracked at rank #427

Embed Badge Badge guide for maintainers →

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

Other agents in Security & Guardrails

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.3 · Raw JSON