updated 2026-08-04 02:30 UTC

loushang

zhnt/loushang

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

Coding Agents Python Grade D Listed Apache-2.0
22.9/100
Rank #441 of 468
Compare loushang

How does it stack up against its Coding Agents 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 D · 1/5 signals
Last push
2026-08-04 · 0d ago
Recent change
New

Is loushang safe? loushang scores 22.9/100 (Grade D), ranked #441 of 468 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; 30% of recent commits are signed; last pushed 2026-08-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#52 zeroshot — 25.7 (D) → #53 Nanocoder — 23.8 (D) → #55 Plandex — 21.1 (D) → #56 SWE-AF — 20.7 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-03
Newly Listed
First tracked at rank #441
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 loushang View Coding Agents Report missing data
78.4
Activity sub-score · out of 100
#54
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 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-08-04 02:30 UTC · Repo last pushed today

Rank Trend

2026-08-03 2026-08-04

Activity & Reach

Stars
992
Forks
171
Last Push
2026-08-04
today
Commits (4 wk)
699
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
24
Rank Change
=
was #441

Analysis

HVTrust Dimensions vs Coding Agents

22.9 / 100 · 50.0% confidence

loushang Coding Agents average (59 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.5 / 25
6.9 below avg 8.4
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
2.9 below avg 11.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.2 above avg 14.8
AdoptionLog-scaled stars · package downloads
7.2 / 20
5.4 below avg 12.6

Activity Inputs

78.4 / 100
StarsRepository reach
18.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.4 / 20

Supply Chain Trust

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

Is loushang safe?

Public trust evidence for loushang 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 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?
No OpenSSF Scorecard data is currently published for loushang. 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 loushang actively maintained?
Actively maintained. The repository was pushed to within the last 1 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?
30% 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
medium 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 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
Listed 1
2026-08-03
Newly Listed
First tracked at rank #441
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 22.9 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON