Is Fence safe to use?

Fence has an HVTrust score of 58.8/100 (Grade C), ranked #487 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Fence?

Fence scores 58.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 949 GitHub stars and is categorized under Sandboxes & Runtimes.

Fence

fencesandbox/fence

Lightweight, container-free sandbox for running commands with network and filesystem restrictions

Sandboxes & Runtimes Go Grade C Listed Apache-2.0

58.8/100

Rank #487 of 1320

Compare Fence

How does it stack up against its Sandboxes & Runtimes 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-09-01 · 3d ago

Recent change

Rank +8

Is Fence safe? Fence scores 58.8/100 (Grade C), ranked #487 of 1320 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 7.1/10; 79% of recent commits are signed; last pushed 2026-09-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Sandboxes & Runtimes

#4 OpenShell — 69.9 (B) → #5 Container Use — 59.4 (C) → #7 Daytona — 58.3 (C) → #8 Agent Infra Sandbox — 54.1 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 14 spots (#473 → #487)

2026-09-03

Rank Moved

Rank dropped 15 spots (#458 → #473)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with BoxLite Get email alerts for Fence View Sandboxes & Runtimes Report missing data

61.3

Activity sub-score · out of 100

In Sandboxes & Runtimes

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-08-11 2026-09-04

Activity & Reach

Stars

949

Forks

Last Push

2026-09-01

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼14

was #473

Analysis

HVTrust Dimensions vs Sandboxes & Runtimes

58.8 / 100 · 100.0% confidence

Fence Sandboxes & Runtimes average (10 agents)

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

12.8 / 25

1.4 above avg 11.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.7 below avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

2.2 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.6 / 20

1.5 below avg 15.1

AdoptionLog-scaled stars · package downloads

7.1 / 20

5.1 below avg 12.2

Activity Inputs

61.3 / 100

StarsRepository reach

17.9 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

11.3 / 25

CommunityFork signal

7.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.1 / 10

OpenSSF Scorecard · scanned Sep 4, 2026

Signed Commits

79%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 10

Token-Permissions 10

Vulnerabilities 10

Is Fence safe?

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

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

Does Fence have an OpenSSF Scorecard?

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

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

What license does Fence use?

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

Are Fence's commits signed?

79% of the last 100 commits to Fence 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 Fence head-to-head

Fence vs BoxLite → Fence vs E2B → Fence vs Cube Sandbox →

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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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 Fence'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-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-02

Provider Removed

Runtime surface shrank — no longer detected: Redis

Maintain Fence?

For maintainers

HVTrust scores Fence 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-09-04

Rank Moved

Rank dropped 14 spots (#473 → #487)

2026-09-03

Rank Moved

Rank dropped 15 spots (#458 → #473)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-02

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-09-02

Rank Moved

Rank dropped 42 spots (#416 → #458)

2026-09-01

Rank Moved

Rank rose 20 spots (#436 → #416)

2026-08-31

Rank Moved

Rank dropped 49 spots (#387 → #436)

2026-08-30

Rank Moved

Rank rose 10 spots (#397 → #387)

2026-08-29

Rank Moved

Rank dropped 25 spots (#372 → #397)

2026-08-26

Scorecard Added

OSSF Scorecard: 7.1/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 605 spots (#969 → #364)

2026-08-26

HVTrust Changed

HVTrust up 37.8pts (22.2 → 60.0)

2026-08-24

Rank Moved

Rank dropped 11 spots (#960 → #971)

2026-08-18

Rank Moved

Rank rose 12 spots (#969 → #957)

2026-08-17

Rank Moved

Rank rose 14 spots (#983 → #969)

2026-08-16

Rank Moved

Rank dropped 33 spots (#950 → #983)

2026-08-13

Rank Moved

Rank dropped 14 spots (#937 → #951)

2026-08-12

Rank Moved

Rank rose 10 spots (#947 → #937)

2026-08-10

Newly Listed

First tracked at rank #939

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Sandboxes & Runtimes

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