Is Hypit safe to use?

Hypit has an HVTrust score of 75.6/100 (Grade B), ranked #217 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Hypit?

Hypit scores 75.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 17.5k GitHub stars and is categorized under Workflow Platforms.

Hypit

Repository

Website

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

Workflow Platforms TypeScript Listed NOASSERTION Source-available

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

OSSF Scorecard No result

Provenance Attested

Signed commits 49%

Last push yesterday

Advisories None known

Compare Hypit

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Hypit scores 75.6/100 (Grade B), ranked #217 of 1343 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; no OSSF Scorecard result yet; 49% of recent commits are signed; no published advisory affects its latest release (@hypit/hypit); last pushed 2026-09-28. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +16.7 → 92.3 A · #1 of 26
Sign every commit49% signed today +2.5 → 78.1 B · #6 of 26

Already done? Suggest a correction Add the trust badge

How Hypit compares in Workflow Platforms

Bars show each HVTrust score; the tick marks Hypit’s 75.6.

Where the 75.6 comes from

HVTrust dimensions vs the Workflow Platforms average

75.6 / 100 · 100.0% confidence

Hypit Workflow Platforms average (26 agents)

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

10.0 / 25

in line with avg 10.2

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.1 above avg 11.9

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.8 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

2.8 above avg 17.1

AdoptionLog-scaled stars · package downloads

15.5 / 20

2.8 above avg 12.7

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-09-29

Newly Listed

First tracked at rank #217

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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 Hypit View Workflow Platforms Report missing data

90.8

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 B 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 →

Activity & Reach

Stars

17.5k

Forks

2.1k

Last Push

2026-09-28

yesterday

Commits (4 wk)

563

Downloads (7d)

9,998

npm

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

Activity Inputs

90.8 / 100

StarsRepository reach

25.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

49%

of last 100 commits verified

Common questions about Hypit

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Hypit may have internal security practices not visible through public signals.

Public supply-chain signals for Hypit are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Hypit carries less obvious unverified-evidence risk than projects with thin signals.

Does Hypit publish package provenance?

Yes. Hypit's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Hypit have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Hypit. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Hypit actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Hypit use?

Hypit ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Hypit's commits signed?

49% of the last 100 commits to Hypit 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 Hypit head-to-head

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

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

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

browser

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 Hypit?

For maintainers

HVTrust scores Hypit 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-09-29

Newly Listed

First tracked at rank #217

GitHub → Website → npm: @hypit/hypit

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/hypit.svg)](https://hvtracker.net/agents/hypit)
            
HTML:
            <a href="https://hvtracker.net/agents/hypit"><img src="https://hvtracker.net/badge/hypit.svg" alt="HVTrust"></a>

Other agents in Workflow Platforms

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