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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 132 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
308
Forks
46
Last Push
2026-01-23
132 days ago
Commits (4 wk)
0
Downloads (7d)
157
pypi
HN mentions (30d)
4
Open Issues
13
Rank Change
▼7
was #158
Analysis
HVTrust Dimensions
43.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
8.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.1 / 17
MaintenanceFreshness and commits
3.2 / 20
AdoptionStars and downloads
8.9 / 20
Activity Inputs
29.5 / 100
StarsRepository reach
14.9 / 30
FreshnessLast push recency
6.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.8 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.2 / 10
via deps.dev · OpenSSF
Signed Commits
67%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection4
CI-Tests5
CII-Best-Practices0
Code-Review6
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies1
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Sotopia agents safe?
Public trust evidence for Sotopia agents 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 Sotopia agents publish package provenance?
No published build provenance is currently detected for Sotopia agents. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Sotopia agents have an OpenSSF Scorecard?
Sotopia agents has an OpenSSF Scorecard score of 4.2/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 Sotopia agents actively maintained?
Slowing down. Last push was 132 days ago — keep an eye on whether activity resumes.
What license does Sotopia agents use?
Sotopia agents ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Sotopia agents's commits signed?
67% of the last 100 commits to Sotopia agents 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 Sotopia agents?
HVTrust scores Sotopia agents 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.
