WrenAI

GenBI (Generative BI) for AI agents, an open-source, governed text-to-SQL through an open context layer that turns natur

Research & Data Python Grade A Listed NOASSERTION
86.1/100
Rank #41 of 1308
Compare WrenAI

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-25 · 0d ago
Recent change
Rank

Is WrenAI safe? WrenAI scores 86.1/100 (Grade A), ranked #41 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.7/10; 96% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-08-18
Rank Moved
Rank rose 11 spots (#40 → #29)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.
87.6
Activity sub-score · out of 100
#3

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-25 07:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
17.4k
Forks
2.0k
Last Push
2026-08-25
today
Commits (4 wk)
56
Downloads (7d)
99
pypi
HN mentions (30d)
Open Issues
260
Rank Change
▼4
was #37

Analysis

HVTrust Dimensions vs Research & Data

86.1 / 100 · 100.0% confidence

WrenAI Research & Data average (32 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.4 / 25
12.7 above avg 6.7
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.3 above avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
2.2 above avg 11.1
Maintenance60% last-push freshness · 40% commit activity
19.0 / 20
6.5 above avg 12.5
AdoptionLog-scaled stars · package downloads
12.8 / 20
1.8 above avg 11.0

Activity Inputs

87.6 / 100
StarsRepository reach
25.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
21.9 / 25
CommunityFork signal
15.3 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.7 / 10
OpenSSF Scorecard · scanned Aug 24, 2026
Signed Commits
96%
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 10
Fuzzing 0
License 9
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is WrenAI safe?

Public supply-chain signals for WrenAI are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but WrenAI carries less obvious unverified-evidence risk than projects with thin signals.
Does WrenAI publish package provenance?
Yes. WrenAI's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does WrenAI have an OpenSSF Scorecard?
WrenAI has an OpenSSF Scorecard score of 5.7/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 WrenAI actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does WrenAI use?
WrenAI ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are WrenAI's commits signed?
96% of the last 100 commits to WrenAI 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.

Compare WrenAI head-to-head

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
WrenAI appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 WrenAI'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-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-07-13
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-06-05
Provenance Added
Package provenance attestation detected

Maintain WrenAI?

For maintainers

HVTrust scores WrenAI 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
Score 1HVTrust 1Provenance 1MCP 1Surface 1Rank 1
2026-08-18
Rank Moved
Rank rose 11 spots (#40 → #29)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-07-13
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-06-05
Provenance Added
Package provenance attestation detected
2026-05-29
HVTrust Changed
HVTrust up 9.9pts (56.2 → 66.1)
2026-05-28
Activity Score Changed
Activity score up 24pts (65 → 90)

Embed Badge Badge guide for maintainers →

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

Other agents in Research & Data

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON