OpenScience

The open-source AI workbench for scientific research

Research & Data TypeScript Listed Apache-2.0

Is OpenScience safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10
Provenance Attested
Signed commits 56%
Last push today
Advisories None known
Compare OpenScience
Suggest a correction

In detail: OpenScience scores 82.3/100 (Grade A), ranked #118 of 1346 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.5/10; 56% of recent commits are signed; no published advisory affects its latest release (@synsci/openscience); last pushed 2026-10-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenScience 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 OpenScience and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install.

  1. Source Partly signed

    github.com/synthetic-sciences/openscience, Apache-2.0, last pushed 2026-10-03. 56% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies7
    All 18 Scorecard checks
    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 7
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 0
  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @synsci/openscience 2.0.147. No published advisory affects it (OSV, checked 2026-10-03).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues OpenScience’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 OpenScience compares in Research & Data

  1. #3 Firecrawl 88.0 +5.7
  2. #4 WrenAI 85.4 +3.1
  3. #5 OpenScience 82.3 this agent
  4. #6 Crawl4AI 70.2 −12.1
  5. #7 GPT Researcher 68.8 −13.5

Bars show each HVTrust score; the tick marks OpenScience’s 82.3.

Where the 82.3 comes from

HVTrust dimensions vs the Research & Data average

82.3 / 100 · 100.0% confidence

OpenScience Research & Data average (36 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.2 / 25
9.2 above avg 8.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.2 above avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
1.6 above avg 11.6
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.8 above avg 13.2
AdoptionLog-scaled stars · package downloads
13.6 / 20
2.8 above avg 10.8

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Cohere, DeepSeek, Groq, OpenAI, OpenRouter, xAI Grok
2026-09-24
Mcp Status Changed
Detected MCP server support changed: none → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
84.2
Activity sub-score · out of 100
#5

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-10-03 16:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-03

Activity & Reach

Stars
3.9k
Forks
517
Last Push
2026-10-03
today
Commits (4 wk)
488
Downloads (7d)
5,746
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▲2
was #120

Analysis

Activity Inputs

84.2 / 100
StarsRepository reach
21.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.6 / 20

Common questions about OpenScience

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.5/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?
56% 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

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: No explicit API-key/config marker detected.
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-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Cohere, DeepSeek, Groq, OpenAI, OpenRouter, xAI Grok
2026-09-24
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-07
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini
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.

Reputation Timeline

Signal history
Rank 6Listed 2Grade 2Surface 2Surface 1Delisted 1HVTrust 1Provenance 1MCP 1Surface 1
2026-09-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Cohere, DeepSeek, Groq, OpenAI, OpenRouter, xAI Grok
2026-09-24
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-24
Rank Moved
Rank dropped 34 spots (#81 → #115)
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 518 spots (#599 → #81)
2026-09-23
HVTrust Changed
HVTrust up 51.3pts (33.9 → 85.2)
2026-09-22
Newly Listed
First tracked at rank #599
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank dropped 15 spots (#117 → #132)
2026-09-16
Rank Moved
Rank dropped 13 spots (#104 → #117)
2026-09-07
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini
2026-09-05
Rank Moved
Rank dropped 24 spots (#79 → #103)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 82.3 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.4 · Raw JSON