Is open-connector safe to use?

open-connector has an HVTrust score of 60.5/100 (Grade C), ranked #687 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for open-connector?

open-connector scores 60.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.2k GitHub stars and is categorized under Protocols & Tool Integration.

open-connector

Repository Website

Open-source auth gateway connecting 1500+ SaaS providers to AI agents through SDK, CLI, MCP, HTTP, and OpenAPI.

Protocols & Tool Integration TypeScript Listed NOASSERTION Source-available

Is open-connector safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10

Provenance None

Signed commits 77%

Last push today

Compare open-connector

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Suggest a correction

In detail: open-connector scores 60.5/100 (Grade C), ranked #687 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 77% of recent commits are signed; last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How open-connector 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.

Raise the OSSF Scorecard from 5.0 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +8.3 → 68.8 B · #21 of 63
Sign every commit77% signed today +1.1 → 61.6 C · #40 of 63

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships open-connector and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/oomol-lab/open-connector, NOASSERTION, last pushed 2026-11-05. 77% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Nov 2, 2026). The checks that decide who can get a change released:
- Code Review2
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies4
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies 4

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. open-connector is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-10-28 License changed from Apache-2.0 to NOASSERTION
2026-08-27 OSSF Scorecard: 4.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues open-connector’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 open-connector compares in Protocols & Tool Integration

Bars show each HVTrust score; the tick marks open-connector’s 60.5.

Where the 60.5 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

60.5 / 100 · 100.0% confidence

open-connector Protocols & Tool Integration average (63 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.1 / 25

1.0 below avg 11.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

in line with avg 13.0

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.5 above avg 14.5

AdoptionLog-scaled stars · package downloads

9.1 / 20

2.0 below avg 11.1

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-28

License Changed

License changed from Apache-2.0 to NOASSERTION

2026-10-28

Rank Moved

Rank dropped 57 spots (#618 → #675)

2026-10-19

Rank Moved

Rank dropped 12 spots (#600 → #612)

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.

Compare with another agent View Protocols & Tool Integration Report missing data

85.6

Activity sub-score · out of 100

#41

In Protocols & Tool Integration

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars

6.2k

Forks

588

Last Push

2026-11-05

today

Commits (4 wk)

207

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #689

Analysis

Activity Inputs

85.6 / 100

StarsRepository reach

22.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

12.9 / 20

Common questions about open-connector

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. open-connector may have internal security practices not visible through public signals.

open-connector 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 open-connector publish package provenance?

No published build provenance is currently detected for open-connector. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does open-connector have an OpenSSF Scorecard?

open-connector 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 open-connector actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does open-connector use?

open-connector ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are open-connector's commits signed?

77% of the last 100 commits to open-connector 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

medium 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.

Postgres

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Marketplace

Marketplace plugin/integration surface detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 open-connector'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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

Maintain open-connector?

For maintainers

HVTrust scores open-connector 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

2026-10-28

License Changed

License changed from Apache-2.0 to NOASSERTION

2026-10-28

Rank Moved

Rank dropped 57 spots (#618 → #675)

2026-10-19

Rank Moved

Rank dropped 12 spots (#600 → #612)

2026-10-16

Rank Moved

Rank rose 48 spots (#641 → #593)

2026-10-05

Rank Moved

Rank dropped 49 spots (#572 → #621)

2026-09-28

Rank Moved

Rank rose 14 spots (#573 → #559)

2026-09-27

Rank Moved

Rank rose 46 spots (#619 → #573)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Rank Moved

Rank dropped 271 spots (#343 → #614)

2026-09-23

HVTrust Changed

HVTrust up 9.9pts (50.5 → 60.4)

2026-09-22

Newly Listed

First tracked at rank #343

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank rose 25 spots (#651 → #626)

2026-09-11

Rank Moved

Rank dropped 15 spots (#632 → #647)

2026-09-10

Rank Moved

Rank dropped 49 spots (#583 → #632)

2026-09-08

Rank Moved

Rank dropped 17 spots (#564 → #581)

2026-09-07

Rank Moved

Rank dropped 38 spots (#526 → #564)

2026-09-06

Rank Moved

Rank dropped 10 spots (#516 → #526)

2026-09-05

Rank Moved

Rank dropped 67 spots (#449 → #516)

2026-09-04

Rank Moved

Rank dropped 16 spots (#433 → #449)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-03

Rank Moved

Rank dropped 83 spots (#350 → #433)

2026-09-02

Rank Moved

Rank rose 14 spots (#364 → #350)

2026-09-01

Rank Moved

Rank dropped 15 spots (#349 → #364)

2026-08-31

Rank Moved

Rank dropped 26 spots (#323 → #349)

2026-08-30

Rank Moved

Rank rose 10 spots (#333 → #323)

2026-08-27

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-27

Grade Changed

Trust grade D → C

2026-08-27

Rank Moved

Rank rose 612 spots (#940 → #328)

2026-08-27

HVTrust Changed

HVTrust up 36.2pts (26.0 → 62.2)

2026-08-26

Rank Moved

Rank dropped 112 spots (#828 → #940)

2026-08-24

Rank Moved

Rank dropped 10 spots (#817 → #827)

2026-08-16

Rank Moved

Rank dropped 16 spots (#813 → #829)

2026-08-10

Rank Moved

Rank dropped 43 spots (#769 → #812)

2026-08-08

Rank Moved

Rank dropped 327 spots (#434 → #761)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/open-connector.svg)](https://hvtracker.net/agents/open-connector)
            
HTML:
            <a href="https://hvtracker.net/agents/open-connector"><img src="https://hvtracker.net/badge/open-connector.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

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

open-connector

How open-connector could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How open-connector compares in Protocols & Tool Integration

Where the 60.5 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about open-connector

AI agent surface

Maintain open-connector?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Protocols & Tool Integration