Is Headcount safe to use?

Headcount has an HVTrust score of 57.8/100 (Grade C), ranked #103 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Headcount?

Headcount scores 57.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.3k GitHub stars and is categorized under Agent Skills.

Headcount

cbrock84/headcount

An agent organization for Claude Code, structured as a company — 15+ departments, 125+ skills, each independently instal

Agent Skills Markdown Grade C Listed MIT

57.8/100

Rank #103 of 351

Compare Headcount

How does it stack up against its Agent Skills 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-03 · 6d ago

Recent change

Scorecard +4

Is Headcount safe? Headcount scores 57.8/100 (Grade C), ranked #103 of 351 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 4.3/10; 65% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#101 Flow Next — 58.0 (C) → #102 Vibe Coding Prompt Template — 57.9 (C) → #104 Plinth — 57.7 (C) → #105 Agent Skill Creator — 57.6 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-09

Scorecard Added

OSSF Scorecard: 4.3/10

2026-09-09

Grade Changed

Trust grade D → C

2026-09-09

Rank Moved

Rank rose 218 spots (#321 → #103)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/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 Headcount View Agent Skills Report missing data

77.0

Activity sub-score · out of 100

#103

In Agent Skills

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

Activity & Reach

Stars

1.3k

Forks

206

Last Push

2026-09-03

6 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲218

was #321

Analysis

HVTrust Dimensions vs Agent Skills

57.8 / 100 · 100.0% confidence

Headcount Agent Skills average (351 agents)

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

8.6 / 25

1.1 above avg 7.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 11.9

Maintenance60% last-push freshness · 40% commit activity

19.0 / 20

4.6 above avg 14.4

AdoptionLog-scaled stars · package downloads

7.5 / 20

1.3 below avg 8.8

Activity Inputs

77.0 / 100

StarsRepository reach

18.8 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

23.2 / 25

CommunityFork signal

10.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 9, 2026

Signed Commits

65%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Is Headcount safe?

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

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

Does Headcount have an OpenSSF Scorecard?

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

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

What license does Headcount use?

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

Are Headcount's commits signed?

65% of the last 100 commits to Headcount 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

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

Maintain Headcount?

For maintainers

HVTrust scores Headcount 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-09

Scorecard Added

OSSF Scorecard: 4.3/10

2026-09-09

Grade Changed

Trust grade D → C

2026-09-09

Rank Moved

Rank rose 218 spots (#321 → #103)

2026-09-09

HVTrust Changed

HVTrust up 33.5pts (24.3 → 57.8)

2026-09-08

Newly Listed

First tracked at rank #321

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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