Fence vs LayerFS
Both are Grade C and 1.6 points apart, so choose on what you weigh most. Fence leads on supply-chain integrity and transparency; LayerFS leads on maintenance and adoption.
Lightweight, container-free sandbox for running commands with network and filesystem restrictions
Choose Fence if supply-chain integrity and transparency matter most.
- +5.5Safety / Integrity: 79% of recent commits signed, against 23%
- +1.9Transparency: OSSF Scorecard 6.8 against 4.6
Ephemeral Workspaces, durable shared history. LayerFS gives every agent a complete, writable filesystem Workspace over shared committed history, without copying the base. Agents work in parallel, commit what changed as deduplicated checkpoints, then branch, rewind or merge. Try it with LayerFS ×…
Choose LayerFS if maintenance and adoption matter most.
- +8.2Maintenance: last push 1d ago, against 5d ago
- +1.1Adoption: 2.9k GitHub stars against 1k
Where they differ
1 dimension identical: Identity 10.8 · Full evidence table
An independent, evidence-based trust comparison of Fence and LayerFS, two Sandboxes & Runtimes projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | Fencefencesandbox/fence | LayerFSEphemeral-AI-Lab/layerfs |
|---|---|---|
| HVTrust score | 56.4 | 58.0 |
| Evidence grade | C | C |
| Coverage grade | C | C |
| Overall rank | #818 | #765 |
| Rank in Sandboxes & Runtimes | #7 | #6 |
| GitHub stars | 1.0k | 2.9k |
| Last updated | 5d ago | 1d ago |
| Build provenance | No | No |
| OSSF Scorecard | 6.8 / 10 | 4.6 / 10 |
| License | Apache-2.0 | MIT |
| Downloads | — | — |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 12.4 | 6.9 |
| Identity & provenance / 18 | 10.8 | 10.8 |
| Transparency / 17 | 14.3 | 12.4 |
| Maintenance / 20 | 11.7 | 19.9 |
| Adoption / 20 | 7.2 | 8.3 |
| Runtime capability surface (full matrix) | ||
| MCP server | — | — |
| External providers | — | — |
| Requires API keys | No | No |
| Plugin surface | — | plugins |
| Provenance drift | — | — |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →