updated 2026-08-11 20:02 UTC

InsForge

InsForge/InsForge

The all-in-one, open-source backend platform for agentic coding. InsForge gives your coding agent database, auth, storag

Workflow Platforms TypeScript Grade C Listed Apache-2.0
61.9/100
Rank #300 of 1283
Compare InsForge

How does it stack up against its Workflow Platforms 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-08-11 · 0d ago
Recent change
Rank +1

Is InsForge safe? InsForge scores 61.9/100 (Grade C), ranked #300 of 1283 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 5.4/10; 30% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#12 Conductor — 65.2 (B) → #13 Budibase — 63.2 (C) → #15 Xpert AI — 57.1 (C) → #16 Julep — 56.6 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 20 spots (#281 → #301)
2026-08-08
Rank Moved
Rank dropped 65 spots (#212 → #277)
2026-07-13
Rank Moved
Rank dropped 20 spots (#146 → #166)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.4/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.
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 InsForge View Workflow Platforms Report missing data
88.8
Activity sub-score · out of 100
#14
In Workflow Platforms

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-11 20:02 UTC · Repo last pushed today

Activity & Reach

Stars
12.7k
Forks
1.1k
Last Push
2026-08-11
today
Commits (4 wk)
480
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
55
Rank Change
▲1
was #301

Analysis

HVTrust Dimensions vs Workflow Platforms

61.9 / 100 · 100.0% confidence

InsForge Workflow Platforms average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.2 / 25
2.2 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.7 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
1.8 above avg 18.2
AdoptionLog-scaled stars · package downloads
9.9 / 20
3.0 below avg 12.9

Activity Inputs

88.8 / 100
StarsRepository reach
24.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.2 / 20

Supply Chain Trust

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

Is InsForge safe?

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

For maintainers

HVTrust scores InsForge 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 6Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-10
Rank Moved
Rank dropped 20 spots (#281 → #301)
2026-08-08
Rank Moved
Rank dropped 65 spots (#212 → #277)
2026-07-13
Rank Moved
Rank dropped 20 spots (#146 → #166)
2026-06-25
Rank Moved
Rank dropped 16 spots (#146 → #162)
2026-06-18
Rank Moved
Rank dropped 13 spots (#118 → #131)
2026-06-10
Scorecard Added
OSSF Scorecard: 5.9/10
2026-06-10
Grade Changed
Trust grade D → C
2026-06-10
Rank Moved
Rank rose 85 spots (#203 → #118)
2026-06-10
HVTrust Changed
HVTrust up 37.0pts (25.5 → 62.5)
2026-06-07
Newly Listed
First tracked at rank #199
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Workflow Platforms

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