updated 2026-09-04 23:32 UTC

OpenScience

synthetic-sciences/openscience

The open-source AI workbench for scientific research

Research & Data TypeScript Grade A Listed Apache-2.0
81.7/100
Rank #79 of 1320
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-09-04 · 0d ago
Recent change
Provider Added +1

Is OpenScience safe? OpenScience scores 81.7/100 (Grade A), ranked #79 of 1320 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 5.6/10; 60% 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

#3 Firecrawl — 87.6 (A) → #4 WrenAI — 86.3 (A) → #6 Crawl4AI — 72.1 (B) → #7 GPT Researcher — 69.0 (B) →

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
2026-09-03
Rank Moved
Rank rose 12 spots (#89 → #77)
2026-08-27
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/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.6
Activity sub-score · out of 100
#5
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 A 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 →

Signals refreshed 2026-09-04 23:32 UTC · Repo last pushed today

Rank Trend

2026-08-16 2026-09-04

Activity & Reach

Stars
3.5k
Forks
467
Last Push
2026-09-04
today
Commits (4 wk)
308
Downloads (7d)
8,655
npm
HN mentions (30d)
—
Open Issues
15
Rank Change
▼2
was #77

Analysis

HVTrust Dimensions vs Research & Data

81.7 / 100 · 100.0% confidence

OpenScience Research & Data average (33 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.5 / 25
9.4 above avg 8.1
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.1 above avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.6 above avg 11.7
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.8 above avg 13.2
AdoptionLog-scaled stars · package downloads
13.7 / 20
2.8 above avg 10.9

Activity Inputs

83.6 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.4 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.6 / 10
OpenSSF Scorecard · scanned Aug 30, 2026
Signed Commits
60%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 7
SAST 8
Security-Policy 10
Signed-Releases 0
Token-Permissions 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 5.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 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?
60% 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 Firecrawl →

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
8 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
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
How this surface has changed

Detected changes to OpenScience'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
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek

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
Listed 1Grade 1Rank 1Surface 1
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
2026-09-03
Rank Moved
Rank rose 12 spots (#89 → #77)
2026-08-27
Grade Changed
Trust grade B → A
2026-08-16
Newly Listed
First tracked at rank #74
GitHub → npm: @synsci/openscience

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 81.7 Grade A
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