updated 2026-11-15 04:07 UTC

TrueForge

Repository Website

The open-source agent harness - the runtime layer that turns an LLM into a working agent.

Agent Frameworks TypeScript Listed MIT

Is TrueForge safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.4 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare TrueForge

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: TrueForge scores 67.6/100 (Grade B), ranked #447 of 1387 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 7.4/10; 100% of recent commits are signed; last pushed 2026-11-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How TrueForge 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships TrueForge and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/truefoundry/trueforge, MIT, last pushed 2026-11-14. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.4/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 0

  3. Published packages None

    No registry package. TrueForge is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of TrueForge.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues TrueForge’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.

Signed credential (JSON) How to verify

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 TrueForge compares in Agent Frameworks

  1. #41 LangChain4j 67.9 +0.3
  2. #42 Eliza 67.7 +0.1
  3. #43 TrueForge 67.6 this agent
  4. #44 PraisonAI 67.6 ±0
  5. #45 Mastra 65.7 −1.9

Bars show each HVTrust score; the tick marks TrueForge’s 67.6.

Where the 67.6 comes from

HVTrust dimensions vs the Agent Frameworks average

67.6 / 100 · 100.0% confidence

TrueForge Agent Frameworks average (134 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.3 / 25
4.3 above avg 10.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
14.8 / 17
2.4 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
4.9 above avg 15.0
AdoptionLog-scaled stars · package downloads
9.1 / 20
2.1 below avg 11.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-26
Rank Moved
Rank rose 48 spots (#486 → #438)
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View Agent Frameworks Report missing data
85.6
Activity sub-score · out of 100
#43
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 B 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-11-15 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars
6.5k
Forks
560
Last Push
2026-11-14
yesterday
Commits (4 wk)
169
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
48
Rank Change
▼4
was #443

Analysis

Activity Inputs

85.6 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.8 / 20

Common questions about TrueForge

TrueForge 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 TrueForge publish package provenance?
No published build provenance is currently detected for TrueForge. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does TrueForge have an OpenSSF Scorecard?
TrueForge has an OpenSSF Scorecard score of 7.4/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 TrueForge actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does TrueForge use?
TrueForge ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are TrueForge's commits signed?
100% of the last 100 commits to TrueForge 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium 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 TrueForge?

For maintainers

HVTrust scores TrueForge 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 2Listed 1
2026-10-26
Rank Moved
Rank rose 48 spots (#486 → #438)
2026-10-09
Rank Moved
Rank dropped 12 spots (#466 → #478)
2026-09-29
Newly Listed
First tracked at rank #461
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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