updated 2026-10-09 08:15 UTC

WrenAI

Repository Website

GenBI (Generative BI) for AI agents, an open-source, governed text-to-SQL through an open context layer that turns natural-language questions into trusted dashboards, charts, and SQL across 20+ data sources, such as BigQuery, Snowflake, PostgreSQL, ClickHouse, Amazon Redshift, Databricks and more.

Research & Data Python Listed NOASSERTION

Is WrenAI safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.6 / 10
Provenance Attested
Signed commits 90%
Last push yesterday
Advisories None known
Compare WrenAI

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →
Suggest a correction

In detail: WrenAI scores 85.6/100 (Grade A), ranked #83 of 1371 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.6/10; 90% of recent commits are signed; no published advisory affects its latest release (@wrenai/wren-core-wasm, wren-pydantic); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

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

  1. Source Signed

    github.com/Canner/WrenAI, NOASSERTION, last pushed 2026-10-08. 90% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review7
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 7
    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 2

  3. Published packages Partly attested

  4. What you install today No known advisories

    Latest releases checked: @wrenai/wren-core-wasm 0.4.1, wren-pydantic 0.3.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

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

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues WrenAI’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 WrenAI compares in Research & Data

  1. #2 Firecrawl 88.4 +2.8
  2. #3 Unstructured 87.3 +1.7
  3. #4 WrenAI 85.6 this agent
  4. #5 OpenScience 84.6 −1.0
  5. #6 Crawl4AI 70.7 −14.9

Bars show each HVTrust score; the tick marks WrenAI’s 85.6.

Where the 85.6 comes from

HVTrust dimensions vs the Research & Data average

85.6 / 100 · 100.0% confidence

WrenAI Research & Data average (37 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.0 / 25
11.1 above avg 7.9
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.2 above avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
2.0 above avg 11.3
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
5.6 above avg 12.7
AdoptionLog-scaled stars · package downloads
13.1 / 20
2.6 above avg 10.5

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-02
Rank Moved
Rank dropped 10 spots (#72 → #82)
2026-09-23
Rank Moved
Rank dropped 24 spots (#47 → #71)
2026-09-21
Rank Moved
Rank rose 25 spots (#72 → #47)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.
Compare with Docling Get email alerts for WrenAI View Research & Data Report missing data
85.8
Activity sub-score · out of 100
#4
In Research & Data

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-10-09 08:15 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
17.8k
Forks
2.0k
Last Push
2026-10-08
yesterday
Commits (4 wk)
39
Downloads (7d)
157
npm+pypi
HN mentions (30d)
—
Open Issues
209
Rank Change
▼2
was #81

Analysis

Activity Inputs

85.8 / 100
StarsRepository reach
25.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.0 / 25
CommunityFork signal
15.4 / 20

Common questions about WrenAI

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.6/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?
90% 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

WrenAI vs Docling → WrenAI vs Firecrawl → WrenAI vs Unstructured →

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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 4MCP 1Surface 1
2026-10-02
Rank Moved
Rank dropped 10 spots (#72 → #82)
2026-09-23
Rank Moved
Rank dropped 24 spots (#47 → #71)
2026-09-21
Rank Moved
Rank rose 25 spots (#72 → #47)
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
GitHub → Website → PyPI: wren-pydantic npm: @wrenai/wren-core-wasm

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 85.6 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.4 · Raw JSON