Is Lingxi safe to use?

Lingxi has an HVTrust score of 33.5/100 (Grade D), ranked #684 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Lingxi?

Lingxi scores 33.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 256 GitHub stars and is categorized under Agent Frameworks.

Lingxi

lingxi-agent/Lingxi

Agent Frameworks Python Grade D Listed MIT

33.5/100

Rank #684 of 1204

Compare Lingxi

How does it stack up against its Agent Frameworks 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-04-07 · 124d ago

Recent change

Rank +2

Is Lingxi safe? Lingxi scores 33.5/100 (Grade D), ranked #684 of 1204 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 2.6/10; 32% of recent commits are signed; last pushed 2026-04-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#80 Magentic — 37.1 (D) → #81 Youtu-Agent — 35.0 (D) → #83 II-Agent — 32.8 (D) → #84 AutoAgent — 30.4 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 267 spots (#416 → #683)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.6/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 124 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Lingxi View Agent Frameworks Report missing data

29.5

Activity sub-score · out of 100

#82

In Agent Frameworks

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 →

Activity & Reach

Stars

256

Forks

Last Push

2026-04-07

124 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #683

Analysis

HVTrust Dimensions vs Agent Frameworks

33.5 / 100 · 100.0% confidence

Lingxi Agent Frameworks average (117 agents)

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

4.8 / 25

3.4 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

10.7 / 17

0.9 below avg 11.6

Maintenance60% last-push freshness · 40% commit activity

3.7 / 20

10.6 below avg 14.3

AdoptionLog-scaled stars · package downloads

5.8 / 20

5.6 below avg 11.4

Activity Inputs

29.5 / 100

StarsRepository reach

14.5 / 30

FreshnessLast push recency

7.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.6 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

32%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10

Is Lingxi safe?

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

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

Does Lingxi have an OpenSSF Scorecard?

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

Slowing down. Last push was 124 days ago — keep an eye on whether activity resumes.

What license does Lingxi use?

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

Are Lingxi's commits signed?

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

3 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

1 tags

Broad capability areas detected.

code

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 Lingxi'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-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

2026-07-06

Activity Went Stale

No commits for 90 days

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

Maintain Lingxi?

For maintainers

HVTrust scores Lingxi 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-08-08

Rank Moved

Rank dropped 267 spots (#416 → #683)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

2026-07-29

Rank Moved

Rank dropped 11 spots (#394 → #405)

2026-07-15

Rank Moved

Rank dropped 25 spots (#362 → #387)

2026-07-14

Rank Moved

Rank dropped 20 spots (#342 → #362)

2026-07-13

Rank Moved

Rank dropped 36 spots (#306 → #342)

2026-07-06

Activity Went Stale

No commits for 90 days

2026-06-24

Rank Moved

Rank dropped 35 spots (#253 → #288)

2026-06-23

Rank Moved

Rank dropped 22 spots (#231 → #253)

2026-06-22

Rank Moved

Rank dropped 10 spots (#221 → #231)

2026-06-21

Rank Moved

Rank dropped 14 spots (#207 → #221)

2026-06-18

Rank Moved

Rank dropped 13 spots (#185 → #198)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-06-05

Scorecard Added

OSSF Scorecard: 2.9/10

2026-06-02

Rank Moved

Rank dropped 18 spots (#178 → #196)

2026-06-01

Newly Listed

First tracked at rank #178

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/lingxi.svg)](https://hvtracker.net/agents/lingxi)
            
HTML:
            <a href="https://hvtracker.net/agents/lingxi"><img src="https://hvtracker.net/badge/lingxi.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.2 · Raw JSON