updated 2026-09-29 16:10 UTC

SoL-Pi

Repository Website

SoL-Pi: Scaling Auto-Research Loops for Efficient Agent Harnesses

Research & Data TypeScript Listed MIT

Is SoL-Pi safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 40%
Last push today
Compare SoL-Pi

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →
Suggest a correction

In detail: SoL-Pi scores 23.1/100 (Grade D), ranked #1331 of 1343 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; 40% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How SoL-Pi could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

How SoL-Pi compares in Research & Data

  1. #29 MindSearch 27.5 +4.4
  2. #30 OpenResearch 26.7 +3.6
  3. #31 SoL-Pi 23.1 this agent
  4. #32 Agent Laboratory 23.0 −0.1
  5. #33 DeepAnalyze 22.2 −0.9

Bars show each HVTrust score; the tick marks SoL-Pi’s 23.1.

Where the 23.1 comes from

HVTrust dimensions vs the Research & Data average

23.1 / 100 · 50.0% confidence

SoL-Pi Research & Data average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.0 / 25
6.1 below avg 8.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.1 below avg 11.6
Maintenance60% last-push freshness · 40% commit activity
17.6 / 20
4.4 above avg 13.2
AdoptionLog-scaled stars · package downloads
8.4 / 20
2.4 below avg 10.8

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-29
Newly Listed
First tracked at rank #1331
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for SoL-Pi View Research & Data Report missing data
74.8
Activity sub-score · out of 100
#31
In Research & Data

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-09-29 16:10 UTC · Repo last pushed today

Activity & Reach

Stars
3.2k
Forks
255
Last Push
2026-09-29
today
Commits (4 wk)
25
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
25
Rank Change
NEW

Analysis

Activity Inputs

74.8 / 100
StarsRepository reach
21.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
17.6 / 25
CommunityFork signal
11.2 / 20

Supply Chain Trust

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

Common questions about SoL-Pi

Public trust evidence for SoL-Pi 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 SoL-Pi publish package provenance?
No published build provenance is currently detected for SoL-Pi. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does SoL-Pi have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for SoL-Pi. 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 SoL-Pi actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does SoL-Pi use?
SoL-Pi ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SoL-Pi's commits signed?
40% of the last 100 commits to SoL-Pi 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high 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 SoL-Pi?

For maintainers

HVTrust scores SoL-Pi 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-09-29
Newly Listed
First tracked at rank #1331
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 23.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/sol-pi.svg)](https://hvtracker.net/agents/sol-pi)
HTML:
<a href="https://hvtracker.net/agents/sol-pi"><img src="https://hvtracker.net/badge/sol-pi.svg" alt="HVTrust"></a>

Other agents in Research & Data

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON