updated 2026-11-15 04: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? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 19%
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 67.5/100 (Grade B), ranked #451 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 19% of recent commits are signed; no published advisory affects its latest release (@hypit/hypit); last pushed 2026-11-14. 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-11-14. 19% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

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

  3. Published packages Linked, not attested

    • npm @hypit/hypit Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

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

Changes to this chain

  • 2026-11-12 Package provenance attestation no longer detected
  • 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. #6 Flyte 72.3 +4.8
  2. #7 Nocobase 67.9 +0.4
  3. #8 Hypit 67.5 this agent
  4. #9 Hatchet 67.4 −0.1
  5. #10 Budibase 65.1 −2.4

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

Where the 67.5 comes from

HVTrust dimensions vs the Workflow Platforms average

67.5 / 100 · 100.0% confidence

Hypit Workflow Platforms average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.2 / 25
3.2 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
in line with avg 12.5
Maintenance60% last-push freshness · 40% commit activity
16.4 / 20
in line with avg 16.4
AdoptionLog-scaled stars · package downloads
16.3 / 20
3.4 above avg 12.9

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-12
Provenance Removed
Package provenance attestation no longer detected
2026-11-12
Grade Changed
Trust grade A → B
2026-11-12
Rank Moved
Rank dropped 308 spots (#140 → #448)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with n8n
View Workflow Platforms Report missing data
82.3
Activity sub-score · out of 100
#8
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 →

Signals refreshed 2026-11-15 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars
29.9k
Forks
3.5k
Last Push
2026-11-14
yesterday
Commits (4 wk)
12
Downloads (7d)
14,970
npm
HN mentions (30d)
—
Open Issues
39
Rank Change
▲3
was #454

Analysis

Activity Inputs

82.3 / 100
StarsRepository reach
26.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
16.5 / 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.
Hypit has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Hypit publish package provenance?
No published build provenance is currently detected for Hypit. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Hypit have an OpenSSF Scorecard?
Hypit has an OpenSSF Scorecard score of 5.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 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?
19% 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 Botpress → Hypit vs Trigger.dev →

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
How this surface has changed

Detected changes to Hypit'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.

2026-11-12
Provenance Removed
Package provenance attestation no longer detected

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 7HVTrust 2Grade 2Listed 1Scorecard 1Score 1Provenance 1
2026-11-12
Provenance Removed
Package provenance attestation no longer detected
2026-11-12
Grade Changed
Trust grade A → B
2026-11-12
Rank Moved
Rank dropped 308 spots (#140 → #448)
2026-11-12
HVTrust Changed
HVTrust down 15.1pts (82.6 → 67.5)
2026-11-11
Rank Moved
Rank rose 37 spots (#177 → #140)
2026-11-08
Rank Moved
Rank dropped 39 spots (#142 → #181)
2026-11-08
Activity Score Changed
Activity score down 6pts (87 → 81)
2026-11-07
Rank Moved
Rank dropped 15 spots (#127 → #142)
2026-10-18
Rank Moved
Rank rose 24 spots (#143 → #119)
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 67.5 Grade B
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