Is AIPass safe to use?

AIPass has an HVTrust score of 85.9/100 (Grade A), ranked #44 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for AIPass?

AIPass scores 85.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 260 GitHub stars and is categorized under Multi-Agent Systems.

AIPass

AIOSAI/AIPass

Persistent Agent Workspace — AI agents that remember, collaborate, and never start from zero.

Multi-Agent Systems Python Grade A Listed MIT

85.9/100

Rank #44 of 1308

Compare AIPass

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-19 · 0d ago

Recent change

No recent signal change

Is AIPass safe? AIPass scores 85.9/100 (Grade A), ranked #44 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.5/10; 100% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#2 Solace Agent Mesh — 80.0 (A) → #3 CAMEL — 68.4 (B) → #4 Agency Swarm — 65.2 (B) → #5 Open Multi-Agent — 64.7 (C) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with Solace Agent Mesh Get email alerts for AIPass View Multi-Agent Systems Report missing data

71.8

Activity sub-score · out of 100

In Multi-Agent Systems

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

260

Forks

Last Push

2026-08-19

today

Commits (4 wk)

244

Downloads (7d)

219

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #43

Analysis

HVTrust Dimensions vs Multi-Agent Systems

85.9 / 100 · 100.0% confidence

AIPass Multi-Agent Systems average (36 agents)

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

21.9 / 25

15.8 above avg 6.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.8 above avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

14.9 / 17

4.0 above avg 10.9

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.0 above avg 13.0

AdoptionLog-scaled stars · package downloads

8.9 / 20

1.0 below avg 9.9

Activity Inputs

71.8 / 100

StarsRepository reach

14.5 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

7.3 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

7.5 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 5

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 6

SAST 10

Security-Policy 10

Signed-Releases 8

Token-Permissions 10

Vulnerabilities 8

Is AIPass safe?

Public supply-chain signals for AIPass are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but AIPass carries less obvious unverified-evidence risk than projects with thin signals.

Does AIPass publish package provenance?

Yes. AIPass's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does AIPass have an OpenSSF Scorecard?

AIPass has an OpenSSF Scorecard score of 7.5/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 AIPass actively maintained?

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

What license does AIPass use?

AIPass ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are AIPass's commits signed?

100% of the last 100 commits to AIPass 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 AIPass head-to-head

AIPass vs Solace Agent Mesh → AIPass vs CAMEL → AIPass vs Agency Swarm →

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

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

Extensions

Extension based plugin/integration 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 AIPass'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-07-17

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintain AIPass?

For maintainers

HVTrust scores AIPass 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-07-17

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-05-30

Scorecard Added

OSSF Scorecard: 6.4/10

2026-05-30

Rank Moved

Rank rose 47 spots (#69 → #22)

2026-05-30

HVTrust Changed

HVTrust up 15.8pts (65.1 → 80.9)

2026-05-29

Newly Listed

First tracked at rank #69

GitHub → PyPI: aipass

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Multi-Agent Systems

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