updated 2026-08-04 02:30 UTC

T3MP3ST

elder-plinius/T3MP3ST

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

Security & Guardrails TypeScript Grade D Listed AGPL-3.0
25.0/100
Rank #427 of 468
Compare T3MP3ST

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-02 · 2d ago
Recent change
New

Is T3MP3ST safe? T3MP3ST scores 25.0/100 (Grade D), ranked #427 of 468 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 77% of recent commits are signed; last pushed 2026-08-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#10 Llama Guard — 52.1 (C) → #11 Agentic Security — 49.9 (D) → #12 HexStrike AI — 46.2 (D) → #14 CyberStrike — 24.6 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-03
Newly Listed
First tracked at rank #427
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 T3MP3ST View Security & Guardrails Report missing data
86.5
Activity sub-score · out of 100
#13
In Security & Guardrails

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-04 02:30 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-03 2026-08-04

Activity & Reach

Stars
5.4k
Forks
1.1k
Last Push
2026-08-02
2 days ago
Commits (4 wk)
146
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #427

Analysis

HVTrust Dimensions vs Security & Guardrails

25.0 / 100 · 50.0% confidence

T3MP3ST Security & Guardrails average (14 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
5.2 below avg 9.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
4.0 below avg 12.5
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
3.3 above avg 16.6
AdoptionLog-scaled stars · package downloads
9.0 / 20
1.7 below avg 10.7

Activity Inputs

86.5 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.2 / 20

Supply Chain Trust

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

Is T3MP3ST safe?

Public trust evidence for T3MP3ST 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 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?
No OpenSSF Scorecard data is currently published for T3MP3ST. 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 T3MP3ST actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
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?
77% 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.

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
medium confidence
Extensions
Extension based 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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-08-03
Newly Listed
First tracked at rank #427
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 25.0 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON