---
title: "hyperswitch trust report"
type: "trust-report"
slug: "juspay-hyperswitch"
canonical_url: "https://www.graphcanon.com/tools/juspay-hyperswitch/trust"
computed_at: "2026-07-15T10:49:58.858Z"
maintenance_label: "Very active"
security_status: "findings"
---

# hyperswitch trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and external security intelligence providers. Not a security guarantee._

## Maintenance

- Label: Very active (96% recency signal)
- Days since last push: 0
- Last release: 2026-07-10T07:05:19Z
- Releases (90d): 4
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 552877440
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-15T10:49:58.858Z
- Methodology: github_public_v1

## Security intelligence

- **OSV dependency advisories**: Published findings
  - Last query: 2026-07-15T10:50:00.848839+00:00
  - Evidence: https://osv.dev/
- **deps.dev advisories**: Not queried
  - Evidence: https://deps.dev/
- **OpenSSF Scorecard**: Not queried
  - Evidence: https://api.securityscorecards.dev/projects/github.com/juspay/hyperswitch
  - Note: Weekly public scans omit some checks at scale.

### Findings

- **low**: GHSA-2g4f-4pwh-qvx6 (ajv@6.12.6 · package-lock.json · osv@v1)
- **low**: GHSA-25h7-pfq9-p65f (flatted@3.2.6 · package-lock.json · osv@v1)
- **low**: GHSA-rf6f-7fwh-wjgh (flatted@3.2.6 · package-lock.json · osv@v1)
- **low**: GHSA-2qvq-rjwj-gvw9 (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-2w6w-674q-4c4q (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-3mfm-83xf-c92r (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-442j-39wm-28r2 (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-7rx3-28cr-v5wh (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-9cx6-37pm-9jff (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-xhpv-hc6g-r9c6 (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-xjpj-3mr7-gcpf (handlebars@4.7.8 · package-lock.json · osv@v1)
- **low**: GHSA-hhhv-q57g-882q (jose@4.14.4 · package-lock.json · osv@v1)
- **low**: GHSA-f23m-r3pf-42rh (lodash@4.17.21 · package-lock.json · osv@v1)
- **low**: GHSA-r5fr-rjxr-66jc (lodash@4.17.21 · package-lock.json · osv@v1)
- **low**: GHSA-xxjr-mmjv-4gpg (lodash@4.17.21 · package-lock.json · osv@v1)
- **low**: GHSA-6rw7-vpxm-498p (qs@6.5.3 · package-lock.json · osv@v1)
- **low**: GHSA-w5hq-g745-h8pq (uuid@3.4.0 · package-lock.json · osv@v1)
- **low**: GHSA-qpx9-hpmf-5gmw (underscore@1.12.1 · package-lock.json · osv@v1)

## Method and caveats

These are heuristics from public GitHub data and external security intelligence providers, sourced and dated. 
"No published findings from this source" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is hyperswitch maintained?

GraphCanon rates hyperswitch "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 0 days ago. 4 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is hyperswitch safe to use?

Last scanned today (deps profile). Status: 18 low - 18 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify hyperswitch as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is hyperswitch a fork?

No. hyperswitch is not flagged as a fork in GitHub metadata at the time of the last refresh.

### Does hyperswitch have known security vulnerabilities?

Last scanned today (deps profile). Status: 18 low - 18 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

### How often is the hyperswitch trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).

### What does GraphCanon never claim about hyperswitch?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for hyperswitch. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for hyperswitch?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read [trust methodology](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/juspay-hyperswitch/trust`](/api/graphcanon/tools/juspay-hyperswitch/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_