updated 2026-10-09 12:08 UTC

Trigger.dev

Repository Website

Trigger.dev – build and deploy durable AI agents and workflows

Workflow Platforms TypeScript Listed Apache-2.0

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

OSSF Scorecard 5.8 / 10
Provenance Attested
Signed commits 4%
Last push yesterday
Advisories None known
Compare Trigger.dev

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Trigger.dev scores 86.7/100 (Grade A), ranked #67 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.8/10; 4% of recent commits are signed; no published advisory affects its latest release (@trigger.dev/sdk); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Trigger.dev 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 Trigger.dev 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 Partly signed

    github.com/triggerdotdev/trigger.dev, Apache-2.0, last pushed 2026-10-08. 4% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection4
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 8
    SAST 10
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm @trigger.dev/sdk Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: @trigger.dev/sdk 4.7.3. 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 Trigger.dev.

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 Trigger.dev’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 Trigger.dev compares in Workflow Platforms

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

Bars show each HVTrust score; the tick marks Trigger.dev’s 86.7.

Where the 86.7 comes from

HVTrust dimensions vs the Workflow Platforms average

86.7 / 100 · 100.0% confidence

Trigger.dev Workflow Platforms average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.9 / 25
4.3 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.4 / 17
0.9 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
2.9 above avg 17.0
AdoptionLog-scaled stars · package downloads
18.2 / 20
5.4 above avg 12.8

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-03
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with n8n Get email alerts for Trigger.dev View Workflow Platforms Report missing data
90.0
Activity sub-score · out of 100
#3
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 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 12:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
16.5k
Forks
1.5k
Last Push
2026-10-08
yesterday
Commits (4 wk)
263
Downloads (7d)
1,220,100
npm
HN mentions (30d)
—
Open Issues
173
Rank Change
▼5
was #62

Analysis

Activity Inputs

90.0 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.7 / 20

Common questions about Trigger.dev

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

Trigger.dev vs n8n → Trigger.dev vs Botpress → Trigger.dev vs Hypit →

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
Trigger.dev appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based 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 Trigger.dev'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-10-03
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Anthropic

Maintain Trigger.dev?

For maintainers

HVTrust scores Trigger.dev 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
Surface 1Surface 1
2026-10-03
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
GitHub → Website → npm: @trigger.dev/sdk

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 86.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/trigger-dev.svg)](https://hvtracker.net/agents/trigger-dev)
HTML:
<a href="https://hvtracker.net/agents/trigger-dev"><img src="https://hvtracker.net/badge/trigger-dev.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
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON