Frontman
Website
The AI agent that lives in your framework/browser
Is Frontman safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Frontman
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Frontman scores 42.2/100 (Grade D), ranked #1175 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 100% of recent commits are signed; no published advisory affects its latest release (@frontman-ai/nextjs); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →
How Frontman 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 to 9.0no OSSF Scorecard result yet +37.2 → 79.4 B · #10 of 77
- Publish build provenance for its packagesnpm publish --provenance from CI +33.1 → 75.3 B · #11 of 77
Chain of custody
Scanners check what the code says. This traces who ships Frontman and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/frontman-ai/frontman, NOASSERTION, last pushed 2026-10-17. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages Linked, not attested
- npm @frontman-ai/nextjs Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: @frontman-ai/nextjs 2.0.2. No published advisory affects it (OSV, checked 2026-10-17).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Frontman.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Frontman’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Frontman compares in Coding Agents
- #63 ZCode 44.8 +2.6
- #64 Antigravity CLI 43.7 +1.5
- #65 Frontman 42.2 this agent
- #66 Integuru 40.5 −1.7
- #67 Stakpak Agent 40.1 −2.1
Bars show each HVTrust score; the tick marks Frontman’s 42.2.
Where the 42.2 comes from
HVTrust dimensions vs the Coding Agents average
42.2 / 100 · 67.0% confidenceFrontman Coding Agents average (77 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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
Activity & Reach
Analysis
Activity Inputs
75.0 / 100Common questions about Frontman
Does Frontman publish package provenance?
Does Frontman have an OpenSSF Scorecard?
Is Frontman actively maintained?
What license does Frontman use?
Are Frontman's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Frontman'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.
Maintain Frontman?
For maintainers
HVTrust scores Frontman 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/frontman)
<a href="https://hvtracker.net/agents/frontman"><img src="https://hvtracker.net/badge/frontman.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON