updated 2026-10-13 08:09 UTC

AIPass

Repository Website

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

Multi-Agent Systems Python Listed MIT

Is AIPass safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.3 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare AIPass

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

Pick any agent to compare →
Suggest a correction

In detail: AIPass scores 85.5/100 (Grade A), ranked #86 of 1371 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.3/10; 100% of recent commits are signed; no published advisory affects its latest release (aipass); last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How AIPass 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships AIPass 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 Signed

    github.com/AIOSAI/AIPass, MIT, last pushed 2026-10-13. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.3/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releases6
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies6
    All 18 Scorecard checks
    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 6
    Token-Permissions 10
    Vulnerabilities 8

  3. Published packages Linked and attested

    • PyPI aipass Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: aipass 2.8.12. No published advisory affects it (OSV, checked 2026-10-13).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of AIPass.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues AIPass’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 AIPass compares in Multi-Agent Systems

  1. #1 AIPass 85.5 this agent
  2. #2 OpenMausBot 83.8 −1.7
  3. #3 Swarms 72.9 −12.6
  4. #4 Solace Agent Mesh 68.9 −16.6
  5. #5 Agency Swarm 68.0 −17.5

Bars show each HVTrust score; the tick marks AIPass’s 85.5.

Where the 85.5 comes from

HVTrust dimensions vs the Multi-Agent Systems average

85.5 / 100 · 100.0% confidence

AIPass Multi-Agent Systems average (43 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
21.6 / 25
12.9 above avg 8.7
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.7 above avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
14.7 / 17
2.5 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.9 above avg 13.1
AdoptionLog-scaled stars · package downloads
9.0 / 20
1.2 below avg 10.2

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 24 spots (#41 → #65)
2026-09-21
Rank Moved
Rank rose 14 spots (#54 → #40)
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 OpenMausBot Get email alerts for AIPass View Multi-Agent Systems Report missing data
72.4
Activity sub-score · out of 100
#1
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 →

Signals refreshed 2026-10-13 08:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
288
Forks
43
Last Push
2026-10-13
today
Commits (4 wk)
668
Downloads (7d)
224
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▼2
was #84

Analysis

Activity Inputs

72.4 / 100
StarsRepository reach
14.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
7.6 / 20

Common questions about AIPass

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.3/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 OpenMausBot → AIPass vs Swarms → AIPass vs Solace Agent Mesh →

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
high 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
Rank 2Surface 1
2026-09-23
Rank Moved
Rank dropped 24 spots (#41 → #65)
2026-09-21
Rank Moved
Rank rose 14 spots (#54 → #40)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
GitHub → Website → PyPI: aipass

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 85.5 Grade A
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.4 · Raw JSON