Is Wisp Science safe to use?

Wisp Science has an HVTrust score of 55.2/100 (Grade C), ranked #612 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Wisp Science?

Wisp Science scores 55.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.1k GitHub stars and is categorized under Research & Data.

Wisp Science

xuzhougeng/wisp-science

Open-source, local-first desktop AI research workbench for scientific computing with Python/R, MCP bioinformatics tools,

Research & Data Rust Grade C Listed AGPL-3.0

55.2/100

Rank #612 of 1320

Compare Wisp Science

How does it stack up against its Research & Data 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-04 · 0d ago

Recent change

Rank +11

Is Wisp Science safe? Wisp Science scores 55.2/100 (Grade C), ranked #612 of 1320 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.8/10; 54% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#15 llm-for-zotero — 56.7 (C) → #16 Lumibot — 56.4 (C) → #18 FinRobot — 52.1 (C) → #19 luxas — 49.4 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 17 spots (#595 → #612)

2026-09-03

Tool Surface Changed

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

2026-09-03

Mcp Status Changed

Detected MCP server support changed: implemented → declared

Maintainer Checklist

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

Compare with another agent Get email alerts for Wisp Science View Research & Data Report missing data

77.8

Activity sub-score · out of 100

#17

In Research & Data

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

Activity & Reach

Stars

1.1k

Forks

113

Last Push

2026-09-04

today

Commits (4 wk)

773

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼17

was #595

Analysis

HVTrust Dimensions vs Research & Data

55.2 / 100 · 100.0% confidence

Wisp Science Research & Data average (33 agents)

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

6.2 / 25

1.9 below avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.1 below avg 11.9

Transparency50% declared license · 50% OSSF Scorecard

10.9 / 17

0.8 below avg 11.7

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

6.8 above avg 13.2

AdoptionLog-scaled stars · package downloads

7.3 / 20

3.6 below avg 10.9

Activity Inputs

77.8 / 100

StarsRepository reach

18.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

9.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.8 / 10

OpenSSF Scorecard · scanned Aug 29, 2026

Signed Commits

54%

of last 100 commits verified

Binary-Artifacts 7

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 8

Token-Permissions 0

Vulnerabilities 0

Is Wisp Science safe?

Wisp Science 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 Wisp Science publish package provenance?

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

Does Wisp Science have an OpenSSF Scorecard?

Wisp Science has an OpenSSF Scorecard score of 2.8/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 Wisp Science actively maintained?

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

What license does Wisp Science use?

Wisp Science ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Wisp Science's commits signed?

54% of the last 100 commits to Wisp Science 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

None detected

No clear third-party provider dependency detected.

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

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 Wisp Science'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 → none

2026-09-03

Mcp Status Changed

Detected MCP server support changed: implemented → declared

Maintain Wisp Science?

For maintainers

HVTrust scores Wisp Science 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-04

Rank Moved

Rank dropped 17 spots (#595 → #612)

2026-09-03

Tool Surface Changed

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

2026-09-03

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-09-03

Rank Moved

Rank dropped 19 spots (#576 → #595)

2026-09-02

Rank Moved

Rank dropped 22 spots (#554 → #576)

2026-09-01

Rank Moved

Rank dropped 12 spots (#542 → #554)

2026-08-31

Rank Moved

Rank dropped 30 spots (#512 → #542)

2026-08-29

Scorecard Added

OSSF Scorecard: 2.8/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 501 spots (#1019 → #518)

2026-08-29

HVTrust Changed

HVTrust up 30.2pts (24.4 → 54.6)

2026-08-28

Rank Moved

Rank dropped 37 spots (#982 → #1019)

2026-08-27

Rank Moved

Rank dropped 20 spots (#962 → #982)

2026-08-26

Rank Moved

Rank dropped 104 spots (#858 → #962)

2026-08-24

Rank Moved

Rank dropped 10 spots (#851 → #861)

2026-08-22

Rank Moved

Rank rose 10 spots (#863 → #853)

2026-08-16

Rank Moved

Rank dropped 24 spots (#845 → #869)

2026-08-10

Newly Listed

First tracked at rank #845

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Research & Data

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