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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed today
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
15.2k
Forks
1.3k
Last Push
2026-06-04
today
Commits (4 wk)
146
Downloads (7d)
612,580
npm
HN mentions (30d)
—
Open Issues
338
Rank Change
=
was #12
Analysis
HVTrust Dimensions
90.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
20.6 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
14.0 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
17.8 / 20
Activity Inputs
89.6 / 100
StarsRepository reach
25.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.5 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
6.5 / 10
via deps.dev · OpenSSF
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-Policy0
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 6.5/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.
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
