Wisp Science
Open-source, local-first desktop AI research workbench for scientific computing with Python/R, MCP bioinformatics tools, SSH/WSL/GPU runtimes, and OpenAI/Anthropic models.
Is Wisp Science safe? Promising trust profile, but some evidence still deserves review.
Compare Wisp Science
How does it stack up against its Research & Data neighbours?
Pick any agent to compare →In detail: Wisp Science scores 56.9/100 (Grade C), ranked #721 of 1325 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; 85% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Wisp Science compares in Research & Data
- #13 OpenBB 59.8 +2.9
- #14 SurfSense 59.0 +2.1
- #15 Wisp Science 56.9 this agent
- #16 llm-for-zotero 56.5 −0.4
- #17 Lumibot 55.8 −1.1
Bars show each HVTrust score; the tick marks Wisp Science’s 56.9.
Where the 56.9 comes from
HVTrust dimensions vs the Research & Data average
56.9 / 100 · 100.0% confidenceWisp Science Research & Data average (33 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
78.1 / 100Supply Chain Trust
Common questions about Wisp Science
Does Wisp Science publish package provenance?
Does Wisp Science have an OpenSSF Scorecard?
Is Wisp Science actively maintained?
What license does Wisp Science use?
Are Wisp Science's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/wisp-science)
<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
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