Is SurfSense safe to use?

SurfSense has an HVTrust score of 58.3/100 (Grade C), ranked #361 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SurfSense?

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

SurfSense

MODSetter/SurfSense

Open-source NotebookLM alternative. Research the open web with live data(Reddit, YT, IG, TikTok, Indeed, Google Search,

Research & Data Python Grade C Listed NOASSERTION Source-available

58.3/100

Rank #361 of 1283

Compare SurfSense

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-08 · 3d ago

Recent change

Rank +1

Is SurfSense safe? SurfSense scores 58.3/100 (Grade C), ranked #361 of 1283 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.9/10; 11% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#9 Maxun — 61.8 (C) → #10 OpenBB — 60.4 (C) → #12 Lumibot — 56.8 (C) → #13 FinRobot — 49.2 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 16 spots (#342 → #358)

2026-08-08

Rank Moved

Rank dropped 83 spots (#257 → #340)

2026-07-31

Rank Moved

Rank dropped 12 spots (#241 → #253)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.9/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 Get email alerts for SurfSense View Research & Data Report missing data

89.6

Activity sub-score · out of 100

#11

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

Activity & Reach

Stars

15.9k

Forks

1.5k

Last Push

2026-08-08

3 days ago

Commits (4 wk)

680

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

116

Rank Change

▼3

was #358

Analysis

HVTrust Dimensions vs Research & Data

58.3 / 100 · 100.0% confidence

SurfSense Research & Data average (31 agents)

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

5.4 / 25

1.0 below avg 6.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.7 below avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

11.8 / 17

0.8 above avg 11.0

Maintenance60% last-push freshness · 40% commit activity

19.8 / 20

7.3 above avg 12.5

AdoptionLog-scaled stars · package downloads

10.1 / 20

0.8 below avg 10.9

Activity Inputs

89.6 / 100

StarsRepository reach

25.2 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Aug 10, 2026

Signed Commits

11%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is SurfSense safe?

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. SurfSense may have internal security practices not visible through public signals.

SurfSense has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does SurfSense publish package provenance?

No published build provenance is currently detected for SurfSense. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does SurfSense have an OpenSSF Scorecard?

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

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

What license does SurfSense use?

SurfSense ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are SurfSense's commits signed?

11% of the last 100 commits to SurfSense 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

high confidence

Implemented

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

Postgres

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

database

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 SurfSense?

For maintainers

HVTrust scores SurfSense 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-10

Rank Moved

Rank dropped 16 spots (#342 → #358)

2026-08-08

Rank Moved

Rank dropped 83 spots (#257 → #340)

2026-07-31

Rank Moved

Rank dropped 12 spots (#241 → #253)

2026-07-15

Rank Moved

Rank dropped 10 spots (#212 → #222)

2026-07-14

Scorecard Added

OSSF Scorecard: 4.1/10

2026-07-14

Grade Changed

Trust grade D → C

2026-07-14

Rank Moved

Rank rose 147 spots (#359 → #212)

2026-07-14

HVTrust Changed

HVTrust up 33.6pts (25.0 → 58.6)

2026-07-13

Newly Listed

First tracked at rank #359

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/surfsense.svg)](https://hvtracker.net/agents/surfsense)
            
HTML:
            <a href="https://hvtracker.net/agents/surfsense"><img src="https://hvtracker.net/badge/surfsense.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.3 · Raw JSON