Unla has an HVTrust score of 50.3/100 (Grade C), ranked #910 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Unla?

Unla scores 50.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.2k GitHub stars and is categorized under Protocols & Tool Integration.

Unla

AmoyLab/Unla

🧩 MCP Gateway - A lightweight gateway service that instantly transforms existing MCP Servers and APIs into MCP servers w

Protocols & Tool Integration TypeScript Grade C Listed MIT

50.3/100

Rank #910 of 1328

Compare Unla

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

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-08-27 · 24d ago

Recent change

Rank

Is Unla safe? Unla scores 50.3/100 (Grade C), ranked #910 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 4.7/10; 11% of recent commits are signed; last pushed 2026-08-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#45 FastAPI-MCP — 51.7 (C) → #46 MCP Bundles — 51.3 (C) → #48 code-mode — 49.7 (D) → #49 CrewAI tools — 45.9 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-15

Rank Moved

Rank dropped 11 spots (#903 → #914)

2026-09-11

Rank Moved

Rank dropped 15 spots (#885 → #900)

2026-09-09

Rank Moved

Rank dropped 22 spots (#866 → #888)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.7/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.

Compare with another agent Get email alerts for Unla View Protocols & Tool Integration Report missing data

56.2

Activity sub-score · out of 100

#47

In Protocols & Tool Integration

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 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 →

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars

2.2k

Forks

185

Last Push

2026-08-27

24 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #912

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

50.3 / 100 · 100.0% confidence

Unla Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

6.4 / 25

4.1 below avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

in line with avg 12.8

Maintenance60% last-push freshness · 40% commit activity

11.6 / 20

2.4 below avg 14.0

AdoptionLog-scaled stars · package downloads

8.0 / 20

2.6 below avg 10.6

Activity Inputs

56.2 / 100

StarsRepository reach

20.1 / 30

FreshnessLast push recency

21.7 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

10.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.7 / 10

OpenSSF Scorecard · scanned Sep 18, 2026

Signed Commits

11%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 5

Packaging 10

Pinned-Dependencies 0

SAST 9

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Unla safe?

Public trust evidence for Unla 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 Unla publish package provenance?

No published build provenance is currently detected for Unla. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Unla have an OpenSSF Scorecard?

Unla has an OpenSSF Scorecard score of 4.7/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 Unla actively maintained?

Maintained. Last push was 24 days ago.

What license does Unla use?

Unla ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Unla's commits signed?

11% of the last 100 commits to Unla 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

high confidence

Implemented

Unla appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency 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

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 Unla'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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain Unla?

For maintainers

HVTrust scores Unla 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

2026-09-15

Rank Moved

Rank dropped 11 spots (#903 → #914)

2026-09-11

Rank Moved

Rank dropped 15 spots (#885 → #900)

2026-09-09

Rank Moved

Rank dropped 22 spots (#866 → #888)

2026-09-08

Rank Moved

Rank dropped 12 spots (#854 → #866)

2026-09-07

Rank Moved

Rank dropped 51 spots (#803 → #854)

2026-09-06

Rank Moved

Rank dropped 10 spots (#793 → #803)

2026-09-05

Rank Moved

Rank dropped 59 spots (#734 → #793)

2026-09-04

Rank Moved

Rank dropped 13 spots (#721 → #734)

2026-09-03

Rank Moved

Rank dropped 73 spots (#648 → #721)

2026-09-03

Activity Score Changed

Activity score down 8pts (66 → 58)

2026-09-02

Rank Moved

Rank dropped 32 spots (#616 → #648)

2026-09-01

Rank Moved

Rank dropped 20 spots (#596 → #616)

2026-08-31

Rank Moved

Rank dropped 31 spots (#565 → #596)

2026-08-30

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 576 spots (#1141 → #565)

2026-08-30

HVTrust Changed

HVTrust up 30.8pts (21.8 → 52.6)

2026-08-29

Rank Moved

Rank dropped 30 spots (#1111 → #1141)

2026-08-28

Rank Moved

Rank dropped 31 spots (#1080 → #1111)

2026-08-27

Rank Moved

Rank dropped 17 spots (#1063 → #1080)

2026-08-26

Rank Moved

Rank dropped 73 spots (#990 → #1063)

2026-08-24

Rank Moved

Rank dropped 21 spots (#968 → #989)

2026-08-22

Rank Moved

Rank rose 11 spots (#984 → #973)

2026-08-17

Rank Moved

Rank rose 13 spots (#984 → #971)

2026-08-16

Rank Moved

Rank dropped 28 spots (#956 → #984)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank rose 24 spots (#964 → #940)

2026-08-10

Rank Moved

Rank dropped 59 spots (#894 → #953)

2026-08-08

Rank Moved

Rank dropped 442 spots (#479 → #921)

2026-08-06

Newly Listed

First tracked at rank #498

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/unla.svg)](https://hvtracker.net/agents/unla)
            
HTML:
            <a href="https://hvtracker.net/agents/unla"><img src="https://hvtracker.net/badge/unla.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

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