HumanLayer

The best way to get AI coding agents to solve hard problems in complex codebases.

Coding Agents TypeScript Grade C Listed NOASSERTION
50.2/100
Rank #312 of 468
Compare HumanLayer

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-06-19 · 48d ago
Recent change
No recent signal change

Is HumanLayer safe? HumanLayer scores 50.2/100 (Grade C), ranked #312 of 468 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.7/10; 53% of recent commits are signed; last pushed 2026-06-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-15
Rank Moved
Rank dropped 18 spots (#265 → #283)
2026-07-14
Rank Moved
Rank dropped 14 spots (#251 → #265)
2026-07-13
Rank Moved
Rank dropped 29 spots (#222 → #251)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
Refresh maintenance signals The repo was last pushed 48 days ago. Fresh activity helps separate stable projects from stale ones.
56.4
Activity sub-score · out of 100
#39

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 →

Signals refreshed 2026-08-06 05:00 UTC · Repo last pushed 48 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
11.2k
Forks
930
Last Push
2026-06-19
48 days ago
Commits (4 wk)
0?
Downloads (7d)
HN mentions (30d)
Open Issues
59
Rank Change
▼2
was #310

Analysis

HVTrust Dimensions vs Coding Agents

50.2 / 100 · 100.0% confidence

HumanLayer Coding Agents average (59 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.3 / 25
1.0 below avg 8.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 11.3
Maintenance60% last-push freshness · 40% commit activity
8.8 / 20
5.9 below avg 14.7
AdoptionLog-scaled stars · package downloads
9.7 / 20
2.9 below avg 12.6

Activity Inputs

56.4 / 100
StarsRepository reach
24.3 / 30
FreshnessLast push recency
18.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.7 / 10
OpenSSF Scorecard · scanned Aug 5, 2026
Signed Commits
53%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 8
CII-Best-Practices 0
Code-Review 4
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 9
Maintained 0
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is HumanLayer safe?

Public trust evidence for HumanLayer is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does HumanLayer publish package provenance?
No published build provenance is currently detected for HumanLayer. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does HumanLayer have an OpenSSF Scorecard?
HumanLayer has an OpenSSF Scorecard score of 3.7/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 HumanLayer actively maintained?
Slowing down. Last push was 48 days ago — keep an eye on whether activity resumes.
What license does HumanLayer use?
HumanLayer ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are HumanLayer's commits signed?
53% of the last 100 commits to HumanLayer 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
HumanLayer appears to expose MCP server capabilities.
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

Maintain HumanLayer?

For maintainers

HVTrust scores HumanLayer 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 1HVTrust 1Grade 1Scorecard 1
2026-07-15
Rank Moved
Rank dropped 18 spots (#265 → #283)
2026-07-14
Rank Moved
Rank dropped 14 spots (#251 → #265)
2026-07-13
Rank Moved
Rank dropped 29 spots (#222 → #251)
2026-06-24
Scorecard Added
OSSF Scorecard: 3.3/10
2026-06-24
Grade Changed
Trust grade D → C
2026-06-24
Rank Moved
Rank rose 67 spots (#292 → #225)
2026-06-24
HVTrust Changed
HVTrust up 28.9pts (22.0 → 50.9)
2026-06-23
Rank Moved
Rank dropped 14 spots (#278 → #292)
2026-06-21
Rank Moved
Rank dropped 22 spots (#253 → #275)
2026-06-20
Newly Listed
First tracked at rank #253

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/humanlayer.svg)](https://hvtracker.net/agents/humanlayer)
HTML:
<a href="https://hvtracker.net/agents/humanlayer"><img src="https://hvtracker.net/badge/humanlayer.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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.2 · Raw JSON