Is SandBase Harness safe to use?

SandBase Harness has an HVTrust score of 62.8/100 (Grade C), ranked #555 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SandBase Harness?

SandBase Harness scores 62.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 678 GitHub stars and is categorized under Agent Frameworks.

SandBase Harness

Repository

Local-first, self-hosted AI agent runtime and MCP bridge with sandboxed sessions, memory, credentials, audit/replay, and a local Console.

Agent Frameworks TypeScript Listed Apache-2.0

Is SandBase Harness safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10

Provenance None

Signed commits 100%

Last push yesterday

Compare SandBase Harness

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: SandBase Harness scores 62.8/100 (Grade C), ranked #555 of 1343 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 5.5/10; 100% of recent commits are signed; last pushed 2026-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How SandBase Harness 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.

Raise the OSSF Scorecard from 5.5 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +7.2 → 70.0 B · #24 of 125

Already done? Suggest a correction Add the trust badge

How SandBase Harness compares in Agent Frameworks

Bars show each HVTrust score; the tick marks SandBase Harness’s 62.8.

Where the 62.8 comes from

HVTrust dimensions vs the Agent Frameworks average

62.8 / 100 · 100.0% confidence

SandBase Harness Agent Frameworks average (125 agents)

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

11.9 / 25

2.1 above avg 9.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.8 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

5.8 above avg 14.1

AdoptionLog-scaled stars · package downloads

6.8 / 20

4.4 below avg 11.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-01

Rank Moved

Rank dropped 64 spots (#491 → #555)

2026-09-27

Rank Moved

Rank rose 42 spots (#530 → #488)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/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.

Compare with another agent Get email alerts for SandBase Harness View Agent Frameworks Report missing data

75.7

Activity sub-score · out of 100

#49

In Agent Frameworks

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 →

Rank Trend

2026-09-29 2026-09-30

Activity & Reach

Stars

678

Forks

Last Push

2026-09-30

yesterday

Commits (4 wk)

269

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼64

was #491

Analysis

Activity Inputs

75.7 / 100

StarsRepository reach

17.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

8.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Oct 1, 2026

Signed Commits

100%

of last 100 commits verified

Dependency-Update-Tool 10

Code-Review 0

Dangerous-Workflow 10

Security-Policy 10

Token-Permissions 10

Maintained 0

Binary-Artifacts 10

CII-Best-Practices 0

Vulnerabilities 0

Pinned-Dependencies 3

SAST 10

Signed-Releases -1

Packaging 10

License 10

Fuzzing 0

Branch-Protection 0

Contributors 0

CI-Tests 10

Common questions about SandBase Harness

SandBase Harness 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 SandBase Harness publish package provenance?

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

Does SandBase Harness have an OpenSSF Scorecard?

SandBase Harness 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 SandBase Harness actively maintained?

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

What license does SandBase Harness use?

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

Are SandBase Harness's commits signed?

100% of the last 100 commits to SandBase Harness 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

SandBase Harness appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 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

How this surface has changed

Detected changes to SandBase Harness'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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

Maintain SandBase Harness?

For maintainers

HVTrust scores SandBase Harness 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-10-01

Rank Moved

Rank dropped 64 spots (#491 → #555)

2026-09-27

Rank Moved

Rank rose 42 spots (#530 → #488)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 167 spots (#359 → #526)

2026-09-23

HVTrust Changed

HVTrust up 13.5pts (49.7 → 63.2)

2026-09-22

Newly Listed

First tracked at rank #359

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 19 spots (#646 → #627)

2026-09-11

Rank Moved

Rank dropped 10 spots (#635 → #645)

2026-09-07

Rank Moved

Rank dropped 44 spots (#568 → #612)

2026-09-05

Rank Moved

Rank dropped 74 spots (#493 → #567)

2026-09-04

Rank Moved

Rank rose 130 spots (#623 → #493)

2026-09-04

HVTrust Changed

HVTrust up 4.3pts (54.3 → 58.6)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-03

Rank Moved

Rank dropped 35 spots (#588 → #623)

2026-09-02

Rank Moved

Rank dropped 24 spots (#564 → #588)

2026-09-01

Rank Moved

Rank dropped 17 spots (#547 → #564)

2026-08-31

Rank Moved

Rank dropped 32 spots (#515 → #547)

2026-08-30

Rank Moved

Rank rose 10 spots (#525 → #515)

2026-08-29

Rank Moved

Rank dropped 27 spots (#498 → #525)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.4/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 397 spots (#887 → #490)

2026-08-26

HVTrust Changed

HVTrust up 30.4pts (23.7 → 54.1)

2026-08-24

Rank Moved

Rank dropped 13 spots (#870 → #883)

2026-08-23

Rank Moved

Rank rose 11 spots (#881 → #870)

2026-08-20

Rank Moved

Rank rose 10 spots (#895 → #885)

2026-08-16

Newly Listed

First tracked at rank #903

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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