TinyTroupe

LLM-powered multiagent persona simulation for imagination enhancement and business insights.

Multi-Agent Systems Jupyter Notebook Grade C Listed MIT
55.5/100
Rank #403 of 1283
Compare TinyTroupe

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-07-03 · 39d ago
Recent change
Rank +1

Is TinyTroupe safe? TinyTroupe scores 55.5/100 (Grade C), ranked #403 of 1283 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 21% of recent commits are signed; last pushed 2026-07-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 18 spots (#385 → #403)
2026-08-08
Rank Moved
Rank dropped 92 spots (#289 → #381)
2026-07-15
Rank Moved
Rank dropped 12 spots (#242 → #254)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/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 39 days ago. Fresh activity helps separate stable projects from stale ones.
56.1
Activity sub-score · out of 100
#13

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

Signals refreshed 2026-08-11 20:32 UTC · Repo last pushed 39 days ago

Activity & Reach

Stars
7.5k
Forks
676
Last Push
2026-07-03
39 days ago
Commits (4 wk)
0
Downloads (7d)
26
pypi
HN mentions (30d)
0
Open Issues
11
Rank Change
=
was #403

Analysis

HVTrust Dimensions vs Multi-Agent Systems

55.5 / 100 · 100.0% confidence

TinyTroupe Multi-Agent Systems average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
1.7 above avg 6.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
2.2 above avg 11.0
Maintenance60% last-push freshness · 40% commit activity
9.4 / 20
3.6 below avg 13.0
AdoptionLog-scaled stars · package downloads
11.2 / 20
1.2 above avg 10.0

Activity Inputs

56.1 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
19.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.2 / 20

Supply Chain Trust

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

Is TinyTroupe safe?

TinyTroupe 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 TinyTroupe publish package provenance?
No published build provenance is currently detected for TinyTroupe. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does TinyTroupe have an OpenSSF Scorecard?
TinyTroupe has an OpenSSF Scorecard score of 5.5/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 TinyTroupe actively maintained?
Slowing down. Last push was 39 days ago — keep an eye on whether activity resumes.
What license does TinyTroupe use?
TinyTroupe ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are TinyTroupe's commits signed?
21% of the last 100 commits to TinyTroupe 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
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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 TinyTroupe?

For maintainers

HVTrust scores TinyTroupe 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 11HVTrust 3Listed 1Grade 1Scorecard 1Score 1
2026-08-10
Rank Moved
Rank dropped 18 spots (#385 → #403)
2026-08-08
Rank Moved
Rank dropped 92 spots (#289 → #381)
2026-07-15
Rank Moved
Rank dropped 12 spots (#242 → #254)
2026-07-14
Rank Moved
Rank dropped 14 spots (#228 → #242)
2026-07-13
Rank Moved
Rank dropped 30 spots (#198 → #228)
2026-07-03
Rank Moved
Rank rose 15 spots (#226 → #211)
2026-07-03
HVTrust Changed
HVTrust up 3.7pts (51.6 → 55.3)
2026-07-03
Activity Score Changed
Activity score up 8pts (54 → 61)
2026-06-24
Rank Moved
Rank dropped 27 spots (#193 → #220)
2026-06-23
Rank Moved
Rank dropped 13 spots (#180 → #193)
2026-06-21
Rank Moved
Rank dropped 10 spots (#163 → #173)
2026-06-18
Rank Moved
Rank dropped 12 spots (#146 → #158)
2026-06-01
Rank Moved
Rank dropped 16 spots (#105 → #121)
2026-05-29
HVTrust Changed
HVTrust up 9.9pts (44.3 → 54.2)
2026-05-27
Scorecard Added
OSSF Scorecard: 5.9/10
2026-05-27
Grade Changed
Trust grade C → B
2026-05-27
HVTrust Changed
HVTrust up 17.0pts (29.1 → 46.1)
2026-05-25
Newly Listed
First tracked at rank #116

Embed Badge Badge guide for maintainers →

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

Other agents in Multi-Agent Systems

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