Is Trigger.dev safe?
Trigger.dev scores 90.5/100 (Grade A), ranked #7 of 328 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 7.0/10;
100% of recent commits are signed;
last pushed 2026-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
90.5/100 · Grade A
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Transparency
14.4/17
What Would Improve It
Improve transparency to lift the weakest part of the trust profile.
Maintainer Checklist
Keep signals currentTrust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
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 refreshed2026-07-11 04:00 UTC·Repo last pushed yesterday
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
15.6k
Forks
1.3k
Last Push
2026-07-10
yesterday
Commits (4 wk)
241
Downloads (7d)
608,100
npm
HN mentions (30d)
—
Open Issues
319
Rank Change
=
was #7
Analysis
HVTrust Dimensions
90.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
21.2 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
14.4 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
17.8 / 20
Activity Inputs
89.8 / 100
StarsRepository reach
25.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.6 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
7.0 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection4
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies9
SAST10
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
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 7.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 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.
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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
browser
code
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.
Detected MCP server support changed: none → declared
Maintain Trigger.dev?
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.
