Portkey AI Gateway

A blazing fast AI Gateway with integrated guardrails. Route to 1,600+ LLMs, 50+ AI Guardrails with 1 fast & friendly API.

LLM Gateways & Infra TypeScript Listed MIT

Is Portkey AI Gateway safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.8 / 10
Provenance None
Signed commits 74%
Last push 145d ago
Advisories None known
Compare Portkey AI Gateway
Suggest a correction

In detail: Portkey AI Gateway scores 52.1/100 (Grade C), ranked #948 of 1378 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 74% of recent commits are signed; no published advisory affects its latest release (portkey-ai); last pushed 2026-05-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Portkey AI Gateway 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.

Chain of custody

Scanners check what the code says. This traces who ships Portkey AI Gateway 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/Portkey-AI/gateway, MIT, last pushed 2026-05-25. 74% 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 4.8/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Not linked

    • npm portkey-ai Source link points to portkey-ai/portkey-node-sdk, same owner 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: portkey-ai 3.1.0. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-08-07 Provenance drift warning cleared (now: unknown)

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues Portkey AI Gateway’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.

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 Portkey AI Gateway compares in LLM Gateways & Infra

  1. #9 ClawRouter 58.8 +6.7
  2. #10 claude-code-router 57.0 +4.9
  3. #11 Portkey AI Gateway 52.1 this agent
  4. #12 paritok-4b-v1 47.6 −4.5
  5. #13 Chat Nio 37.7 −14.4

Bars show each HVTrust score; the tick marks Portkey AI Gateway’s 52.1.

Where the 52.1 comes from

HVTrust dimensions vs the LLM Gateways & Infra average

52.1 / 100 · 100.0% confidence

Portkey AI Gateway LLM Gateways & Infra average (14 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.7 / 25
0.7 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.7
Maintenance60% last-push freshness · 40% commit activity
2.3 / 20
14.2 below avg 16.5
AdoptionLog-scaled stars · package downloads
17.0 / 20
3.6 above avg 13.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Rank Moved
Rank dropped 12 spots (#931 → #943)
2026-10-14
Rank Moved
Rank dropped 10 spots (#920 → #930)
2026-10-13
Rank Moved
Rank dropped 11 spots (#909 → #920)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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.
Refresh maintenance signals The repo was last pushed 145 days ago. Fresh activity helps separate stable projects from stale ones.
44.3
Activity sub-score · out of 100
#11

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-17 12:07 UTC · Repo last pushed 145 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
13.2k
Forks
1.4k
Last Push
2026-05-25
145 days ago
Commits (4 wk)
0
Downloads (7d)
232,540
npm
HN mentions (30d)
39
Open Issues
133
Rank Change
▼5
was #943

Analysis

Activity Inputs

44.3 / 100
StarsRepository reach
24.7 / 30
FreshnessLast push recency
4.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.6 / 20

Common questions about Portkey AI Gateway

Public trust evidence for Portkey AI Gateway is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Portkey AI Gateway publish package provenance?
No published build provenance is currently detected for Portkey AI Gateway. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Portkey AI Gateway have an OpenSSF Scorecard?
Portkey AI Gateway has an OpenSSF Scorecard score of 4.8/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 Portkey AI Gateway actively maintained?
Slowing down. Last push was 145 days ago — keep an eye on whether activity resumes.
What license does Portkey AI Gateway use?
Portkey AI Gateway ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Portkey AI Gateway's commits signed?
74% of the last 100 commits to Portkey AI Gateway 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.

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
low confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Portkey AI Gateway'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-08-23
Activity Went Stale
No commits for 90 days
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)

Maintain Portkey AI Gateway?

For maintainers

HVTrust scores Portkey AI Gateway 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.

Reputation Timeline

Signal history
Rank 29Grade 3HVTrust 2Drift 1Stale 1
2026-10-16
Rank Moved
Rank dropped 12 spots (#931 → #943)
2026-10-14
Rank Moved
Rank dropped 10 spots (#920 → #930)
2026-10-13
Rank Moved
Rank dropped 11 spots (#909 → #920)
2026-10-09
Rank Moved
Rank dropped 19 spots (#874 → #893)
2026-09-23
Rank Moved
Rank dropped 535 spots (#306 → #841)
2026-09-21
Rank Moved
Rank rose 531 spots (#829 → #298)
2026-09-17
Rank Moved
Rank dropped 17 spots (#802 → #819)
2026-09-11
Rank Moved
Rank dropped 12 spots (#777 → #789)
2026-09-09
Rank Moved
Rank dropped 12 spots (#760 → #772)
2026-09-08
Rank Moved
Rank dropped 11 spots (#749 → #760)
2026-09-07
Rank Moved
Rank dropped 44 spots (#705 → #749)
2026-09-05
Rank Moved
Rank dropped 77 spots (#620 → #697)
2026-09-04
Grade Changed
Trust grade D → C
2026-09-04
Rank Moved
Rank rose 493 spots (#1113 → #620)
2026-09-04
HVTrust Changed
HVTrust up 19.1pts (35.9 → 55.0)
2026-09-03
Grade Changed
Trust grade C → D
2026-09-03
Rank Moved
Rank dropped 547 spots (#566 → #1113)
2026-09-03
HVTrust Changed
HVTrust down 19.1pts (55.0 → 35.9)
2026-09-02
Rank Moved
Rank dropped 24 spots (#542 → #566)
2026-09-01
Rank Moved
Rank dropped 14 spots (#528 → #542)
2026-08-31
Rank Moved
Rank dropped 31 spots (#497 → #528)
2026-08-29
Rank Moved
Rank dropped 23 spots (#479 → #502)
2026-08-27
Rank Moved
Rank dropped 13 spots (#461 → #474)
2026-08-26
Rank Moved
Rank dropped 52 spots (#409 → #461)
2026-08-24
Rank Moved
Rank dropped 23 spots (#389 → #412)
2026-08-23
Activity Went Stale
No commits for 90 days
2026-08-22
Rank Moved
Rank rose 17 spots (#406 → #389)
2026-08-18
Rank Moved
Rank dropped 12 spots (#380 → #392)
2026-08-17
Rank Moved
Rank rose 13 spots (#393 → #380)
2026-08-16
Rank Moved
Rank dropped 13 spots (#380 → #393)
2026-08-13
Rank Moved
Rank dropped 18 spots (#360 → #378)
2026-08-12
Rank Moved
Rank rose 17 spots (#377 → #360)
2026-08-10
Rank Moved
Rank dropped 19 spots (#356 → #375)
2026-08-08
Rank Moved
Rank dropped 88 spots (#266 → #354)
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-08-02
Grade Changed
Trust grade C → D

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/portkey-ai-gateway.svg)](https://hvtracker.net/agents/portkey-ai-gateway)
HTML:
<a href="https://hvtracker.net/agents/portkey-ai-gateway"><img src="https://hvtracker.net/badge/portkey-ai-gateway.svg" alt="HVTrust"></a>

Other agents in LLM Gateways & Infra

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