Is OpenScience safe to use?

OpenScience has an HVTrust score of 78.7/100 (Grade B), ranked #69 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OpenScience?

OpenScience scores 78.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.3k GitHub stars and is categorized under Research & Data.

OpenScience

synthetic-sciences/openscience

The open-source AI workbench for scientific research

Research & Data TypeScript Grade B Listed Apache-2.0

78.7/100

Rank #69 of 1308

Compare OpenScience

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-16 · 1d ago

Recent change

New

Is OpenScience safe? OpenScience scores 78.7/100 (Grade B), ranked #69 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.7/10; 51% of recent commits are signed; last pushed 2026-08-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#2 Unstructured — 86.2 (A) → #3 WrenAI — 86.2 (A) → #5 Firecrawl — 74.0 (B) → #6 DeerFlow — 67.2 (B) →

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Recent Changes

2026-08-16

Newly Listed

First tracked at rank #74

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.

Compare with Docling Get email alerts for OpenScience View Research & Data Report missing data

83.3

Activity sub-score · out of 100

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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-16 2026-08-17

Activity & Reach

Stars

3.3k

Forks

444

Last Push

2026-08-16

yesterday

Commits (4 wk)

143

Downloads (7d)

2,620

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲5

was #74

Analysis

HVTrust Dimensions vs Research & Data

78.7 / 100 · 100.0% confidence

OpenScience Research & Data average (32 agents)

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

15.9 / 25

9.2 above avg 6.7

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.3 above avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

1.4 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

13.0 / 20

2.0 above avg 11.0

Activity Inputs

83.3 / 100

StarsRepository reach

21.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

12.3 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.7 / 10

OpenSSF Scorecard · scanned Aug 16, 2026

Signed Commits

51%

of last 100 commits verified

Maintained 0

Dangerous-Workflow 10

Security-Policy 10

Dependency-Update-Tool 10

Code-Review 0

Packaging -1

Token-Permissions 0

Binary-Artifacts 10

CII-Best-Practices 0

Branch-Protection -1

Signed-Releases 0

Pinned-Dependencies 4

SAST 10

License 10

Fuzzing 0

Contributors 6

CI-Tests 10

Vulnerabilities 0

Is OpenScience safe?

Public supply-chain signals for OpenScience are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but OpenScience carries less obvious unverified-evidence risk than projects with thin signals.

Does OpenScience publish package provenance?

Yes. OpenScience's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does OpenScience have an OpenSSF Scorecard?

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

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

What license does OpenScience use?

OpenScience ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are OpenScience's commits signed?

51% of the last 100 commits to OpenScience 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.

Compare OpenScience head-to-head

OpenScience vs Docling → OpenScience vs Unstructured → OpenScience vs WrenAI →

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

high confidence

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

code

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain OpenScience?

For maintainers

HVTrust scores OpenScience 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-16

Newly Listed

First tracked at rank #74

GitHub → npm: @synsci/openscience

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Research & Data

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON