How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 00:07 UTC·Repo last pushed 10 days ago
Rank Trend
2026-06-022026-06-03
Activity & Reach
Stars
11.9k
Forks
1.1k
Last Push
2026-05-25
10 days ago
Commits (4 wk)
8
Downloads (7d)
156,750
npm
HN mentions (30d)
29
Open Issues
185
Rank Change
▼2
was #166
Analysis
HVTrust Dimensions
41.1 / 100 · 75.0% confidence
Safety / IntegrityOSSF, provenance, signatures
3.7 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
15.1 / 20
AdoptionStars and downloads
16.7 / 20
Activity Inputs
74.4 / 100
StarsRepository reach
24.5 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
14.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
74%
of last 100 commits verified
Is Portkey AI Gateway safe?
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?
No OpenSSF Scorecard data is currently published for Portkey AI Gateway. 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 Portkey AI Gateway actively maintained?
Maintained. Last push was 10 days ago.
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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Portkey AI Gateway?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
