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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 28 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
7.5k
Forks
662
Last Push
2026-05-07
28 days ago
Commits (4 wk)
0
Downloads (7d)
23
pypi
HN mentions (30d)
0
Open Issues
18
Rank Change
▼10
was #129
Analysis
HVTrust Dimensions
53.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
8.4 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.5 / 17
MaintenanceFreshness and commits
10.1 / 20
AdoptionStars and downloads
11.1 / 20
Activity Inputs
57.5 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
21.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.9 / 10
via deps.dev · OpenSSF
Signed Commits
21%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests6
CII-Best-Practices0
Code-Review7
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained5
Packaging-1
Pinned-Dependencies1
SAST9
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities10
Is TinyTroupe safe?
Public trust evidence for TinyTroupe 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 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.9/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?
Maintained. Last push was 28 days ago.
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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain TinyTroupe?
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.
