Open Science Desktop

Open Science Desktop — local-first, model-agnostic AI research workbench for macOS, Windows & Linux. Open-source Claude Science desktop alternative built on Tauri + MCP + agent skills.

Research & Data TypeScript Listed NOASSERTION

Is Open Science Desktop safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 0%
Last push yesterday
Compare Open Science Desktop
Suggest a correction

In detail: Open Science Desktop scores 54.3/100 (Grade C), ranked #881 of 1387 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 3.0/10; recent commits are unsigned; last pushed 2026-11-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Open Science Desktop could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Open Science Desktop and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/ai4s-research/open-science, NOASSERTION, last pushed 2026-11-14. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.0/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 9
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages None

    No registry package. Open Science Desktop is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-10-18 OSSF Scorecard: 2.9/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Open Science Desktop’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Open Science Desktop compares in Research & Data

  1. #19 Lumibot 55.6 +1.3
  2. #20 Comp AI CRM 54.4 +0.1
  3. #21 Open Science Desktop 54.3 this agent
  4. #22 SoL-Pi 54.2 −0.1
  5. #23 FinRobot 51.2 −3.1

Bars show each HVTrust score; the tick marks Open Science Desktop’s 54.3.

Where the 54.3 comes from

HVTrust dimensions vs the Research & Data average

54.3 / 100 · 100.0% confidence

Open Science Desktop Research & Data average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.8 / 25
4.9 below avg 8.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
0.8 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
6.7 above avg 13.2
AdoptionLog-scaled stars · package downloads
8.0 / 20
2.8 below avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Rank Moved
Rank dropped 10 spots (#873 → #883)
2026-11-07
Rank Moved
Rank rose 19 spots (#892 → #873)
2026-10-27
Rank Moved
Rank dropped 13 spots (#865 → #878)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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
View Research & Data Report missing data
80.9
Activity sub-score · out of 100
#21

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 →

Signals refreshed 2026-11-15 16:08 UTC · Repo last pushed yesterday

Rank Trend

2026-10-15 2026-11-15

Activity & Reach

Stars
2.1k
Forks
231
Last Push
2026-11-14
yesterday
Commits (4 wk)
219
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
27
Rank Change
▼1
was #880

Analysis

Activity Inputs

80.9 / 100
StarsRepository reach
19.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.0 / 20

Common questions about Open Science Desktop

Public trust evidence for Open Science Desktop 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 Open Science Desktop publish package provenance?
No published build provenance is currently detected for Open Science Desktop. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Open Science Desktop have an OpenSSF Scorecard?
Open Science Desktop has an OpenSSF Scorecard score of 3.0/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 Open Science Desktop actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Open Science Desktop use?
Open Science Desktop ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Open Science Desktop's commits signed?
0% of the last 100 commits to Open Science Desktop 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
Implemented
Open Science Desktop appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
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

Maintain Open Science Desktop?

For maintainers

HVTrust scores Open Science Desktop 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
Rank 8Listed 1HVTrust 1Grade 1Scorecard 1
2026-11-10
Rank Moved
Rank dropped 10 spots (#873 → #883)
2026-11-07
Rank Moved
Rank rose 19 spots (#892 → #873)
2026-10-27
Rank Moved
Rank dropped 13 spots (#865 → #878)
2026-10-25
Rank Moved
Rank rose 36 spots (#905 → #869)
2026-10-24
Rank Moved
Rank dropped 13 spots (#892 → #905)
2026-10-22
Rank Moved
Rank rose 18 spots (#918 → #900)
2026-10-20
Rank Moved
Rank rose 17 spots (#944 → #927)
2026-10-18
Scorecard Added
OSSF Scorecard: 2.9/10
2026-10-18
Grade Changed
Trust grade D → C
2026-10-18
Rank Moved
Rank rose 424 spots (#1367 → #943)
2026-10-18
HVTrust Changed
HVTrust up 28.7pts (23.5 → 52.2)
2026-10-15
Newly Listed
First tracked at rank #1362

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/open-science-desktop.svg)](https://hvtracker.net/agents/open-science-desktop)
HTML:
<a href="https://hvtracker.net/agents/open-science-desktop"><img src="https://hvtracker.net/badge/open-science-desktop.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.4 · Raw JSON