updated 2026-08-15 09:32 UTC

Franklin

BlockRunAI/Franklin

The AI agent with a wallet — spends USDC autonomously to get real work done. Apache-2.0, TypeScript.

Agent Frameworks TypeScript Grade D Listed Apache-2.0
23.4/100
Rank #898 of 1283
Compare Franklin

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-13 · 2d ago
Recent change
Tool Surface Changed +3

Is Franklin safe? Franklin scores 23.4/100 (Grade D), ranked #898 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 29% of recent commits are signed; last pushed 2026-08-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#94 waku-agent — 23.5 (D) → #95 BitFun — 23.5 (D) → #97 mcp-agent — 23.2 (D) → #98 AWorld — 22.9 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-12
Rank Moved
Rank dropped 16 spots (#875 → #891)
2026-08-10
Rank Moved
Rank dropped 48 spots (#816 → #864)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Franklin View Agent Frameworks Report missing data
70.6
Activity sub-score · out of 100
#96
In Agent Frameworks

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-15 09:32 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
583
Forks
54
Last Push
2026-08-13
2 days ago
Commits (4 wk)
49
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▲1
was #899

Analysis

HVTrust Dimensions vs Agent Frameworks

23.4 / 100 · 50.0% confidence

Franklin Agent Frameworks average (118 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.4 / 25
6.8 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.1 below avg 11.6
Maintenance60% last-push freshness · 40% commit activity
18.6 / 20
4.4 above avg 14.2
AdoptionLog-scaled stars · package downloads
6.6 / 20
4.8 below avg 11.4

Activity Inputs

70.6 / 100
StarsRepository reach
16.6 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
21.2 / 25
CommunityFork signal
8.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
29%
of last 100 commits verified

Is Franklin safe?

Public trust evidence for Franklin 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 Franklin publish package provenance?
No published build provenance is currently detected for Franklin. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Franklin have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Franklin. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Franklin actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Franklin use?
Franklin ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Franklin's commits signed?
28% of the last 100 commits to Franklin 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
Franklin appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
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 Franklin'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-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared

Maintain Franklin?

For maintainers

HVTrust scores Franklin 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
Rank 3Listed 1Surface 1
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-12
Rank Moved
Rank dropped 16 spots (#875 → #891)
2026-08-10
Rank Moved
Rank dropped 48 spots (#816 → #864)
2026-08-08
Rank Moved
Rank dropped 362 spots (#457 → #819)
2026-08-03
Newly Listed
First tracked at rank #432
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON