Upsonic

Build autonomous AI agents in Python.

Agent Frameworks Python Grade D Listed MIT
41.1/100
Rank #1136 of 1328
Compare Upsonic

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-06-18 · 94d ago
Recent change
Stale

Is Upsonic safe? Upsonic scores 41.1/100 (Grade D), ranked #1136 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.9/10; 48% of recent commits are signed; last pushed 2026-06-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-16
Activity Went Stale
No commits for 90 days
2026-09-12
Rank Moved
Rank dropped 14 spots (#1107 → #1121)
2026-09-09
Rank Moved
Rank dropped 15 spots (#1088 → #1103)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/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 94 days ago. Fresh activity helps separate stable projects from stale ones.
48.7
Activity sub-score · out of 100
#101

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

Signals refreshed 2026-09-20 15:32 UTC · Repo last pushed 94 days ago

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
8.0k
Forks
745
Last Push
2026-06-18
94 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
17
Rank Change
=
was #1136

Analysis

HVTrust Dimensions vs Agent Frameworks

41.1 / 100 · 100.0% confidence

Upsonic Agent Frameworks average (122 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.3 / 25
2.4 below avg 9.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
0.6 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
5.7 / 20
8.2 below avg 13.9
AdoptionLog-scaled stars · package downloads
9.4 / 20
1.8 below avg 11.2

Activity Inputs

48.7 / 100
StarsRepository reach
23.4 / 30
FreshnessLast push recency
11.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.4 / 20

Supply Chain Trust

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

Is Upsonic safe?

Public trust evidence for Upsonic 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 Upsonic publish package provenance?
No published build provenance is currently detected for Upsonic. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Upsonic have an OpenSSF Scorecard?
Upsonic has an OpenSSF Scorecard score of 3.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 Upsonic actively maintained?
Slowing down. Last push was 94 days ago — keep an eye on whether activity resumes.
What license does Upsonic use?
Upsonic ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Upsonic's commits signed?
48% of the last 100 commits to Upsonic 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
15 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
3 tags
Broad capability areas detected.
  • browser
  • database
  • search
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
How this surface has changed

Detected changes to Upsonic's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-16
Activity Went Stale
No commits for 90 days

Maintain Upsonic?

For maintainers

HVTrust scores Upsonic 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 28HVTrust 1Grade 1Scorecard 1Score 1Stale 1
2026-09-16
Activity Went Stale
No commits for 90 days
2026-09-12
Rank Moved
Rank dropped 14 spots (#1107 → #1121)
2026-09-09
Rank Moved
Rank dropped 15 spots (#1088 → #1103)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1078 → #1088)
2026-09-07
Rank Moved
Rank dropped 29 spots (#1049 → #1078)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1035 → #1049)
2026-09-05
Rank Moved
Rank dropped 40 spots (#995 → #1035)
2026-09-04
Rank Moved
Rank dropped 27 spots (#968 → #995)
2026-09-03
Rank Moved
Rank dropped 58 spots (#910 → #968)
2026-09-02
Rank Moved
Rank dropped 53 spots (#857 → #910)
2026-09-01
Rank Moved
Rank dropped 30 spots (#827 → #857)
2026-08-31
Rank Moved
Rank dropped 30 spots (#797 → #827)
2026-08-30
Rank Moved
Rank dropped 31 spots (#766 → #797)
2026-08-29
Rank Moved
Rank dropped 49 spots (#717 → #766)
2026-08-28
Rank Moved
Rank dropped 25 spots (#692 → #717)
2026-08-27
Rank Moved
Rank dropped 22 spots (#670 → #692)
2026-08-26
Rank Moved
Rank dropped 98 spots (#572 → #670)
2026-08-24
Rank Moved
Rank dropped 17 spots (#557 → #574)
2026-08-22
Rank Moved
Rank rose 12 spots (#571 → #559)
2026-08-19
Rank Moved
Rank dropped 22 spots (#542 → #564)
2026-08-13
Rank Moved
Rank dropped 12 spots (#517 → #529)
2026-08-10
Rank Moved
Rank dropped 17 spots (#505 → #522)
2026-08-08
Rank Moved
Rank dropped 137 spots (#364 → #501)
2026-07-29
Rank Moved
Rank dropped 10 spots (#341 → #351)
2026-07-18
Activity Score Changed
Activity score down 6pts (64 → 58)
2026-07-15
Rank Moved
Rank dropped 25 spots (#294 → #319)
2026-07-14
Rank Moved
Rank dropped 13 spots (#281 → #294)
2026-07-13
Rank Moved
Rank dropped 34 spots (#247 → #281)
2026-06-24
Scorecard Added
OSSF Scorecard: 4.5/10
2026-06-24
Grade Changed
Trust grade D → C
2026-06-24
Rank Moved
Rank rose 74 spots (#291 → #217)
2026-06-24
HVTrust Changed
HVTrust up 31.4pts (22.1 → 53.5)
2026-06-23
Rank Moved
Rank dropped 11 spots (#280 → #291)

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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