Is Trigger.dev safe to use?

Trigger.dev has an HVTrust score of 91.2/100 (Grade A), ranked #7 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Trigger.dev?

Trigger.dev scores 91.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 16.1k GitHub stars and is categorized under Workflow Platforms.

Trigger.dev

triggerdotdev/trigger.dev

Trigger.dev – build and deploy fully‑managed AI agents and workflows

Workflow Platforms TypeScript Grade A Listed Apache-2.0

91.2/100

Rank #7 of 1308

Compare Trigger.dev

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

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

No recent signal change

Is Trigger.dev safe? Trigger.dev scores 91.2/100 (Grade A), ranked #7 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 6.7/10; 100% 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 Workflow Platforms

#2 n8n — 89.6 (A) → #3 Botpress — 88.0 (A) → #4 Langflow — 78.9 (B) → #5 Dify — 78.8 (B) →

Quick Trust Read

What Would Improve It

Improve transparency to lift the weakest part of the trust profile.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.7/10. Tighten the weakest checks to improve public safety evidence.

Compare with n8n Get email alerts for Trigger.dev View Workflow Platforms Report missing data

89.9

Activity sub-score · out of 100

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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

16.1k

Forks

1.4k

Last Push

2026-08-25

today

Commits (4 wk)

269

Downloads (7d)

608,100

npm

HN mentions (30d)

—

Open Issues

346

Rank Change

was #7

Analysis

HVTrust Dimensions vs Workflow Platforms

91.2 / 100 · 100.0% confidence

Trigger.dev Workflow Platforms average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.9 / 25

10.7 above avg 10.2

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.3 above avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

14.2 / 17

1.8 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

1.7 above avg 18.3

AdoptionLog-scaled stars · package downloads

17.8 / 20

4.9 above avg 12.9

Activity Inputs

89.9 / 100

StarsRepository reach

25.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.7 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

6.7 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 9

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Trigger.dev safe?

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 6.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 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?

100% 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 Langflow →

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

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

2026-05-28

Activity Score Changed

Activity score up 25pts (64 → 90)

GitHub → npm: @trigger.dev/sdk

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON