Is loushang safe to use?

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

What is the trust score for loushang?

loushang scores 56.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.5k GitHub stars and is categorized under Coding Agents.

loushang

zhnt/loushang

AI-native agent harness for coding workflows by python: multi-model LLM orchestration, stateful sessions, tool governanc

Coding Agents Python Grade C Listed Apache-2.0

56.6/100

Rank #715 of 1328

Compare loushang

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-14 · 4d ago

Recent change

Rank +1

Is loushang safe? loushang scores 56.6/100 (Grade C), ranked #715 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.4/10; 31% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#41 Vercel fx — 57.6 (C) → #42 jcode — 57.3 (C) → #44 freebuff — 56.2 (C) → #45 Stagewise — 55.2 (C) →

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 12 spots (#706 → #718)

2026-09-13

Rank Moved

Rank rose 24 spots (#734 → #710)

2026-09-10

Rank Moved

Rank dropped 10 spots (#718 → #728)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.4/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 loushang View Coding Agents Report missing data

79.7

Activity sub-score · out of 100

#43

In Coding Agents

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

Activity & Reach

Stars

1.5k

Forks

237

Last Push

2026-09-14

4 days ago

Commits (4 wk)

820

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼5

was #710

Analysis

HVTrust Dimensions vs Coding Agents

56.6 / 100 · 100.0% confidence

loushang Coding Agents average (72 agents)

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

7.1 / 25

1.9 below avg 9.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.0 below avg 11.8

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

19.7 / 20

4.8 above avg 14.9

AdoptionLog-scaled stars · package downloads

7.6 / 20

4.6 below avg 12.2

Activity Inputs

79.7 / 100

StarsRepository reach

19.0 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Sep 14, 2026

Signed Commits

31%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is loushang safe?

loushang has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does loushang publish package provenance?

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

Does loushang have an OpenSSF Scorecard?

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

Actively maintained. The repository was pushed to within the last 4 day(s).

What license does loushang use?

loushang ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are loushang's commits signed?

31% of the last 100 commits to loushang 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

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared 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

How this surface has changed

Detected changes to loushang'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-03

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

Maintain loushang?

For maintainers

HVTrust scores loushang 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 12 spots (#706 → #718)

2026-09-13

Rank Moved

Rank rose 24 spots (#734 → #710)

2026-09-10

Rank Moved

Rank dropped 10 spots (#718 → #728)

2026-09-09

Rank Moved

Rank dropped 14 spots (#704 → #718)

2026-09-08

Rank Moved

Rank rose 53 spots (#757 → #704)

2026-09-07

Rank Moved

Rank dropped 39 spots (#718 → #757)

2026-09-06

Rank Moved

Rank dropped 18 spots (#700 → #718)

2026-09-05

Rank Moved

Rank dropped 41 spots (#659 → #700)

2026-09-04

Rank Moved

Rank dropped 20 spots (#639 → #659)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-09-03

Rank Moved

Rank dropped 80 spots (#559 → #639)

2026-09-02

Rank Moved

Rank dropped 15 spots (#544 → #559)

2026-09-01

Rank Moved

Rank dropped 11 spots (#533 → #544)

2026-08-31

Rank Moved

Rank dropped 32 spots (#501 → #533)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.6/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 599 spots (#1100 → #501)

2026-08-30

HVTrust Changed

HVTrust up 31.9pts (23.2 → 55.1)

2026-08-29

Rank Moved

Rank dropped 36 spots (#1064 → #1100)

2026-08-28

Rank Moved

Rank dropped 28 spots (#1036 → #1064)

2026-08-27

Rank Moved

Rank dropped 23 spots (#1013 → #1036)

2026-08-26

Rank Moved

Rank dropped 92 spots (#921 → #1013)

2026-08-22

Rank Moved

Rank rose 10 spots (#926 → #916)

2026-08-16

Rank Moved

Rank dropped 26 spots (#911 → #937)

2026-08-10

Rank Moved

Rank dropped 53 spots (#860 → #913)

2026-08-08

Rank Moved

Rank dropped 389 spots (#468 → #857)

2026-08-03

Newly Listed

First tracked at rank #441

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

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