Botpress

The open-source hub to build & deploy GPT/LLM Agents ⚡️

Workflow Platforms TypeScript Listed MIT

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

OSSF Scorecard 6.0 / 10
Provenance Attested
Signed commits 99%
Last push 2d ago
Advisories None known
Compare Botpress

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Botpress scores 86.8/100 (Grade A), ranked #63 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 99% of recent commits are signed; no published advisory affects its latest release (@botpress/client); last pushed 2026-10-07. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Chain of custody

Scanners check what the code says. This traces who ships Botpress 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/botpress/botpress, MIT, last pushed 2026-10-07. 99% 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 6.0/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • 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 -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Linked and attested

    • npm @botpress/client Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: @botpress/client 2.8.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 Botpress.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

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

Verify this score yourself

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

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 Botpress compares in Workflow Platforms

  1. #1 n8n 91.5 +4.7
  2. #2 Botpress 86.8 this agent
  3. #3 Trigger.dev 86.7 −0.1
  4. #4 Hypit 82.1 −4.7
  5. #5 Dify 79.1 −7.7

Bars show each HVTrust score; the tick marks Botpress’s 86.8.

Where the 86.8 comes from

HVTrust dimensions vs the Workflow Platforms average

86.8 / 100 · 100.0% confidence

Botpress Workflow Platforms average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.0 / 25
9.4 above avg 10.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.1 above avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
13.6 / 17
1.1 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
18.0 / 20
1.0 above avg 17.0
AdoptionLog-scaled stars · package downloads
15.5 / 20
2.7 above avg 12.8

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 15 spots (#43 → #58)
2026-09-21
Rank Moved
Rank rose 19 spots (#61 → #42)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.
84.6
Activity sub-score · out of 100
#2

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

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

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
14.9k
Forks
2.3k
Last Push
2026-10-07
2 days ago
Commits (4 wk)
33
Downloads (7d)
14,021
npm
HN mentions (30d)
12
Open Issues
11
Rank Change
▲1
was #64

Analysis

Activity Inputs

84.6 / 100
StarsRepository reach
25.0 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
19.1 / 25
CommunityFork signal
15.6 / 20

Common questions about Botpress

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

Maintain Botpress?

For maintainers

HVTrust scores Botpress 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
Rank 13HVTrust 10Grade 10Surface 1
2026-09-23
Rank Moved
Rank dropped 15 spots (#43 → #58)
2026-09-21
Rank Moved
Rank rose 19 spots (#61 → #42)
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 356 spots (#402 → #46)
2026-09-05
HVTrust Changed
HVTrust up 24.5pts (62.4 → 86.9)
2026-09-03
Rank Moved
Rank dropped 25 spots (#370 → #395)
2026-09-02
Grade Changed
Trust grade A → C
2026-09-02
Rank Moved
Rank dropped 336 spots (#34 → #370)
2026-09-02
HVTrust Changed
HVTrust down 24.6pts (86.9 → 62.3)
2026-08-31
Grade Changed
Trust grade C → A
2026-08-31
Rank Moved
Rank rose 286 spots (#320 → #34)
2026-08-31
HVTrust Changed
HVTrust up 24.6pts (62.3 → 86.9)
2026-08-30
Grade Changed
Trust grade A → C
2026-08-30
Rank Moved
Rank dropped 286 spots (#34 → #320)
2026-08-30
HVTrust Changed
HVTrust down 24.6pts (86.9 → 62.3)
2026-08-24
Grade Changed
Trust grade C → A
2026-08-24
Rank Moved
Rank rose 226 spots (#253 → #27)
2026-08-24
HVTrust Changed
HVTrust up 24.6pts (63.5 → 88.1)
2026-08-22
Grade Changed
Trust grade A → C
2026-08-22
Rank Moved
Rank dropped 231 spots (#25 → #256)
2026-08-22
HVTrust Changed
HVTrust down 24.7pts (88.2 → 63.5)
2026-08-19
Grade Changed
Trust grade C → A
2026-08-19
Rank Moved
Rank rose 238 spots (#265 → #27)
2026-08-19
HVTrust Changed
HVTrust up 24.3pts (63.0 → 87.3)
2026-08-17
Grade Changed
Trust grade A → C
2026-08-17
Rank Moved
Rank dropped 242 spots (#27 → #269)
2026-08-17
HVTrust Changed
HVTrust down 24.3pts (87.2 → 62.9)
2026-08-13
Grade Changed
Trust grade C → A
2026-08-13
Rank Moved
Rank rose 228 spots (#250 → #22)
2026-08-13
HVTrust Changed
HVTrust up 24.5pts (63.5 → 88.0)
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: OpenAI
2026-08-12
Grade Changed
Trust grade A → C
2026-08-12
Rank Moved
Rank dropped 224 spots (#26 → #250)
2026-08-12
HVTrust Changed
HVTrust down 24.3pts (87.8 → 63.5)

Embed Badge Badge guide for maintainers →

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

Other agents in Workflow Platforms

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