updated 2026-10-16 16:07 UTC

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 3.2 / 10
Provenance Attested
Signed commits 20%
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 81.3/100 (Grade A), ranked #142 of 1378 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 3.2/10; 20% of recent commits are signed; no published advisory affects its latest release (@hypit/hypit); last pushed 2026-10-15. 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Hypit 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/hypit-ai/hypit, NOASSERTION, last pushed 2026-10-15. 20% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review2
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 5
    CII-Best-Practices 0
    Code-Review 2
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 9
    Maintained 0
    Packaging 10
    Pinned-Dependencies 1
    SAST 5
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm @hypit/hypit Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: @hypit/hypit 0.3.1. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-10-04 OSSF Scorecard: 3.2/10

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 Hypit’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 Hypit compares in Workflow Platforms

  1. #2 Trigger.dev 87.0 +5.7
  2. #3 Botpress 86.9 +5.6
  3. #4 Hypit 81.3 this agent
  4. #5 Langflow 79.0 −2.3
  5. #6 Dify 78.6 −2.7

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

Where the 81.3 comes from

HVTrust dimensions vs the Workflow Platforms average

81.3 / 100 · 100.0% confidence

Hypit Workflow Platforms average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.5 / 25
2.0 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.1 above avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
11.2 / 17
1.4 below avg 12.6
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
2.7 above avg 17.2
AdoptionLog-scaled stars · package downloads
15.7 / 20
2.9 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-11
Rank Moved
Rank dropped 10 spots (#134 → #144)
2026-10-04
Scorecard Added
OSSF Scorecard: 3.2/10
2026-10-04
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.2/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 Hypit View Workflow Platforms Report missing data
91.9
Activity sub-score · out of 100
#4
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-16 16:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
22.8k
Forks
2.6k
Last Push
2026-10-15
yesterday
Commits (4 wk)
247
Downloads (7d)
8,934
npm
HN mentions (30d)
—
Open Issues
11
Rank Change
=
was #142

Analysis

Activity Inputs

91.9 / 100
StarsRepository reach
26.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.9 / 20

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?
Hypit has an OpenSSF Scorecard score of 3.2/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 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?
20% 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
None detected
No clear plugin system or broad tool surface detected.
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
Rank 2Listed 1HVTrust 1Grade 1Scorecard 1
2026-10-11
Rank Moved
Rank dropped 10 spots (#134 → #144)
2026-10-04
Scorecard Added
OSSF Scorecard: 3.2/10
2026-10-04
Grade Changed
Trust grade B → A
2026-10-04
Rank Moved
Rank rose 103 spots (#221 → #118)
2026-10-04
HVTrust Changed
HVTrust up 6.7pts (75.5 → 82.2)
2026-09-29
Newly Listed
First tracked at rank #218
GitHub → Website → npm: @hypit/hypit

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 81.3 Grade A
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON